Ticket - Wiki Integration enhancement/suggestion

[Cullen Newsom <cullennewsom@…>]

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

[Christian Boos]

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).

[Christian Boos]

See also likely duplicate #7015.

[Christian Boos]

#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.

[Ryan J Ollos]

Retargeting tickets that I think won't be completed for 1.1.5, but please move back if I'm incorrect.

[Ryan J Ollos]

Narrowing focus for milestone:1.2. Please move ticket to milestone:1.2 if you intend to fix it.

[Ryan J Ollos]

Milestone renamed

[Ryan J Ollos]

Milestone renamed