Opened 17 years ago
Last modified 9 years ago
#5999 new enhancement
From ticket to wiki : add links to ticket/comment metadata when appropriate
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | ticket system | Version: | |
Severity: | normal | Keywords: | components |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
In a ticket, we have several metadata that relates to something existing in the Trac system: milestone, component, etc.
It would be helpful to have these fields link to their actual wiki page (or to a template-based url, defined in the configuration file):
- the milestone field would redirect to the milestone page,
- the component would redirect to the component view in the milestone page,
Plus, in case these would exist as well in the near future:
- each keyword could redirect to a search page looking for every item with this keyword,
- each person (reporter, owner, on cc list, anyone who adds to the ticket) could redirect to a user page summarizing done and pending work in the whole Trac.
While not adding direct context to a ticket, it would make it easier to access data related to it, without a need for a manually typed search or several clicks.
Attachments (0)
Change History (5)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
The milestone and component links as described above are a must IMO.
Would be much appreciated if rescheduled to 0.11 ;) and maybe only solved for those two parts.
comment:3 by , 17 years ago
It's already the case for the milestone (see #449). For the component, well, there's nothing to redirect to for now… that's why it's a 0.12 thing.
comment:4 by , 14 years ago
Keywords: | components added |
---|---|
Owner: | changed from | to
comment:5 by , 9 years ago
Owner: | removed |
---|
Depending on how site-specific these semantics are (the user one for example), a plugin may make sense here.