Edgewall Software
Modify

Opened 12 years ago

Closed 12 years ago

#7411 closed enhancement (duplicate)

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: Branch:
Release Notes:
API Changes:
Internal Changes:

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 (2)

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

Download all attachments as: .zip

Change History (7)

by Ivan G Shevchenko <linuxadmin@…>, 12 years ago

by Ivan G Shevchenko <linuxadmin@…>, 12 years ago

Attachment: trac 02 view ticket.jpg added

comment:1 by Ivan G Shevchenko <linuxadmin@…>, 12 years ago

Summary: Components (inside the ticket system) should be accessible through the wiki.Components [ticket system] should be accessible through the wiki (see attachments)

in reply to:  description comment:2 by Ivan G Shevchenko <linuxadmin@…>, 12 years ago

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? ;)

comment:3 by Noah Kantrowitz, 12 years ago

Resolution: wontfix
Status: newclosed

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 comment:4 by Christian Boos, 12 years ago

Resolution: wontfix
Status: closedreopened

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.

comment:5 by Christian Boos, 12 years ago

Resolution: duplicate
Status: reopenedclosed

See #1233.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.