Edgewall Software

Opened 15 years ago

Last modified 17 months ago

#5211 new enhancement

Ticket - Wiki Integration enhancement/suggestion

Reported by: Cullen Newsom <cullennewsom@…> Owned by:
Priority: normal Milestone: next-dev-1.7.x
Component: ticket system Version:
Severity: minor Keywords: tracobject component
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:


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

Change History (15)

comment:1 by Christian Boos, 15 years ago

Keywords: tracobject added
Milestone: 0.12
Owner: changed from Jonas Borgström to 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).

comment:2 by anonymous, 14 years ago

Keywords: component added

comment:3 by Christian Boos, 14 years ago

See also likely duplicate #7015.

comment:4 by Christian Boos, 12 years ago

Priority: lownormal

#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 by Pedro Gea <pedrogea@…>, 12 years ago

Cc: pedrogea@… added

comment:6 by Ryan J Ollos, 7 years ago

Milestone: next-major-releases1.1.5

comment:7 by Pedro Gea <pedrogea@…>, 7 years ago

Cc: pedrogea@… removed

comment:8 by Ryan J Ollos, 7 years ago


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

comment:9 by Ryan J Ollos, 7 years ago

Owner: changed from Christian Boos to Ryan J Ollos
Status: newassigned

comment:10 by Ryan J Ollos, 7 years ago

Milestone: 1.1.6next-dev-1.1.x
Owner: Ryan J Ollos removed
Status: assignednew

comment:11 by Ryan J Ollos, 7 years ago

Milestone: next-dev-1.1.xnext-dev-1.3.x

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

comment:12 by Ryan J Ollos, 7 years ago

Milestone: next-dev-1.3.xnext-dev-1.1.x

comment:13 by Ryan J Ollos, 6 years ago

Milestone: next-dev-1.1.xnext-dev-1.3.x

comment:14 by Ryan J Ollos, 3 years ago

Milestone: next-dev-1.3.xnext-dev-1.5.x

Milestone renamed

comment:15 by Ryan J Ollos, 17 months ago

Milestone: next-dev-1.5.xnext-dev-1.7.x

Milestone renamed

Modify Ticket

Change Properties
Set your email in Preferences
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment

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