Ticket #5211 (new enhancement)
Opened 5 years ago
Last modified 17 months ago
Ticket - Wiki Integration enhancement/suggestion
| Reported by: | Cullen Newsom <cullennewsom@…> | Owned by: | cboos |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-0.1X |
| Component: | ticket system | Version: | |
| Severity: | minor | Keywords: | tracobject component |
| Cc: | pedrogea@… | ||
| Release Notes: | |||
| API Changes: | |||
Description
Supposing that one used CamelCase to name their components, and that one then created wiki pages for their components; how about having the 'Component' column of reports created by the ticket system contain clickable links for each component that has a wiki page created for it. Also perhaps, in the case that components do not have a page already created; those components might have a link to create the wiki page.
Thanks,
Cullen
Attachments
Change History
comment:1 Changed 5 years ago by cboos
- Keywords tracobject added
- Milestone set to 0.12
- Owner changed from jonas to cboos
comment:2 Changed 4 years ago by anonymous
- Keywords component added
comment:3 Changed 4 years ago by cboos
See also likely duplicate #7015.
comment:4 Changed 19 months ago by cboos
- Priority changed from low to normal
#9226 was closed as duplicate.
As Remy expressed some interest in ticket:1233#comment:9 to approach this problem via a TicketComponents macro, I'll use this one for my longer term alternative: have 'component' resources and component:... links.
comment:5 Changed 17 months ago by Pedro Gea <pedrogea@…>
- Cc pedrogea@… added



The CamelCase convention is not mandatory for the WikiPageNames. The wiki: TracLinks prefix can be used as well, so that e.g. a wiki:"ticket system" page could be created for the ticket system component.
This will be better handled by making components full-fledged Trac resources.
In this perspective, the link to the component will be a link to the main page for the component resource.
I wonder if it makes sense to have the link in the report, though. In order to not overload the report with too many links, I think I'd prefer to have that link on the ticket page, like we're planning to do for the Milestone field (#449).