Link to queries from ticket fields

[anonymous]

As above

it would be cool to have a way to associate some "report" with "component". This way, when one view ticket, one could click on "component" link and appropriate report would appear.

Dima

[Christopher Lenz]

This could be done with the new ticket query module I guess. I assume the query results should only display active tickets against the component, eh?

[Christopher Lenz]

Summary adjusted to indicate a broader scope. If we link from component names, why not also link from versions etc?

[Christopher Lenz]

See also #449.

[Christian Boos]

I'd say that we should actually link to the corresponding objects from the ticket fields, not to queries.

The milestone field should link to the corresponding milestone, the component and version fields could in the future link to the corresponding objects.

[garyo]

Just adding a "me too" here; either this or #449, as long as the milestone in the ticket view becomes clickable and takes you to the milestone.

[Christian Boos]

I think #449 should be preferred. When you click on e.g. the field "milestone: 0.10" of the ticket, you expect to see more details about 0.10 itself, not a list of tickets. What query should that be anyway? All the 0.10 tickets? All the opened ones only? Better go to the milestone page and get a better overview of the related tickets from there.

Same thing once more fields will correspond to plain resources, like the components and the versions. It makes more sense to go directly to the page corresponding to those things rather than to come up with some arbitrary query. If this is wanted, specific [[TicketQuery]] could be used in those object Wiki descriptions.