Edgewall Software

Ticket #7411 (closed enhancement: duplicate)

Opened 6 months ago

Last modified 6 months ago

Components [ticket system] should be accessible through the wiki (see attachments)

Reported by: Ivan G Shevchenko <linuxadmin@…> Owned by:
Priority: normal Milestone:
Component: ticket system Version: 0.11
Severity: major Keywords: tickets components wiki
Cc:

Description

it is very annoying, that one have to: 1) create components inside the admin-tickets section 2) create SAME components inside the wiki

what if i have dozens of components?

while i am sure, that i'm not the first one to notice this issue, i couldn't find existing tickets about it, sorry. perhaps, if someone find such tickets, he could link my attachments there.

slightly offtopic: is a feature planned that will enable grouping components into (let's say) trees?

Attachments

trac 01 admin components.jpg (59.8 KB) - added by Ivan G Shevchenko <linuxadmin@…> 6 months ago.
trac 02 view ticket.jpg (34.5 KB) - added by Ivan G Shevchenko <linuxadmin@…> 6 months ago.

Change History

Changed 6 months ago by Ivan G Shevchenko <linuxadmin@…>

Changed 6 months ago by Ivan G Shevchenko <linuxadmin@…>

  Changed 6 months ago by Ivan G Shevchenko <linuxadmin@…>

  • summary changed from Components (inside the ticket system) should be accessible through the wiki. to Components [ticket system] should be accessible through the wiki (see attachments)

in reply to: ↑ description   Changed 6 months ago by Ivan G Shevchenko <linuxadmin@…>

by the way: what's the point of adding descriptions to components?

admin / ticket system / components

where can i read it? am i missing something? ;)

follow-up: ↓ 4   Changed 6 months ago by nkantrowitz

  • status changed from new to closed
  • resolution set to wontfix

There is no explicit tie between the wiki and ticket systems. If you want to make wiki pages for them, you are certainly able to, but you are implying those additional semantics, not Trac. You are correct in that we should remove the description field or find a way to show it to the user though. I'm sure there is a separate ticket about that somewhere.

in reply to: ↑ 3   Changed 6 months ago by cboos

  • status changed from closed to reopened
  • resolution wontfix deleted

Replying to nkantrowitz:

There is no explicit tie between the wiki and ticket systems. If you want to make wiki pages for them, you are certainly able to, but you are implying those additional semantics, not Trac. You are correct in that we should remove the description field or find a way to show it to the user though. I'm sure there is a separate ticket about that somewhere.

Now that you acknowledge there's an issue, either:

  • close as duplicate, taking the time to find the actual original ticket
  • if there's none, keep that ticket as a reminder to fix the issue

But closing as wontfix doesn't make sense.

  Changed 6 months ago by cboos

  • status changed from reopened to closed
  • resolution set to duplicate

See #1233.

Add/Change #7411 (Components [ticket system] should be accessible through the wiki (see attachments))

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
to The owner will change from (none). Next status will be 'closed'
 
Note: See TracTickets for help on using tickets.