Edgewall Software
Modify

Opened 15 years ago

Closed 13 years ago

Last modified 12 years ago

#832 closed enhancement (wontfix)

Link to queries from ticket fields

Reported by: anonymous Owned by: Christian Boos
Priority: normal Milestone:
Component: general Version: devel
Severity: minor Keywords: tracobject
Cc: Branch:
Release Notes:
API Changes:

Description

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

Attachments (0)

Change History (7)

comment:1 by vittorio, 15 years ago

Severity: normalenhancement

comment:2 by Christopher Lenz, 15 years ago

Milestone: 0.8Someday

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?

comment:3 by Christopher Lenz, 15 years ago

Summary: Feature request: associate "default" report with componentLink to queries from ticket fields

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

comment:4 by Christopher Lenz, 15 years ago

See also #449.

comment:5 by Christian Boos, 14 years ago

Keywords: tracobject added
Owner: changed from Jonas Borgström to Christian Boos
Severity: normalminor

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.

comment:6 by garyo, 13 years ago

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.

comment:7 by Christian Boos, 13 years ago

Resolution: wontfix
Status: newclosed

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.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Christian Boos.
The resolution will be deleted. Next status will be 'reopened'.
to as closed The owner will be changed from Christian Boos to the specified user.

Add Comment


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