Edgewall Software
Modify

Ticket #7411 (closed enhancement: duplicate)

Opened 4 years ago

Last modified 4 years 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:
Release Notes:
API 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

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

Download all attachments as: .zip

Change History

Changed 4 years ago by Ivan G Shevchenko <linuxadmin@…>

Changed 4 years ago by Ivan G Shevchenko <linuxadmin@…>

comment:1 Changed 4 years 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)

comment:2 in reply to: ↑ description Changed 4 years 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? ;)

comment:3 follow-up: Changed 4 years ago by nkantrowitz

  • Resolution set to wontfix
  • Status changed from new to closed

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.

comment:4 in reply to: ↑ 3 Changed 4 years ago by cboos

  • Resolution wontfix deleted
  • Status changed from closed to reopened

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 Changed 4 years ago by cboos

  • Resolution set to duplicate
  • Status changed from reopened to closed

See #1233.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
to The owner will be changed from (none). Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.