Edgewall Software
Modify

Ticket #832 (closed enhancement: wontfix)

Opened 8 years ago

Last modified 5 years ago

Link to queries from ticket fields

Reported by: anonymous Owned by: cboos
Priority: normal Milestone:
Component: general Version: devel
Severity: minor Keywords: tracobject
Cc:
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

Change History

comment:1 Changed 8 years ago by vittorio

  • Severity changed from normal to enhancement

comment:2 Changed 8 years ago by cmlenz

  • Milestone changed from 0.8 to Someday

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 Changed 8 years ago by cmlenz

  • Summary changed from Feature request: associate "default" report with component to Link 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 Changed 8 years ago by cmlenz

See also #449.

comment:5 Changed 6 years ago by cboos

  • Keywords tracobject added
  • Owner changed from jonas to cboos
  • Severity changed from normal to minor

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 Changed 6 years ago by 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.

comment:7 Changed 5 years ago by cboos

  • Resolution set to wontfix
  • Status changed from new to closed

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.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
to The owner will be changed from cboos. Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.