Edgewall Software
Modify

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#10231 closed enhancement (duplicate)

[PATCH] Add 'root' option to queries to show all descendants of ticket

Reported by: matt sable Owned by:
Priority: normal Milestone:
Component: query system Version:
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:

Description

We can specify parents≤id> and get all the tickets that are direct children of a specified ticket. This patch allows users to be able to see ALL the descendants of such a ticket if root≤id> is used.

Attachments (1)

root_patch_file.diff (2.8 KB ) - added by matt sable 8 years ago.
Patch

Download all attachments as: .zip

Change History (5)

by matt sable, 8 years ago

Attachment: root_patch_file.diff added

Patch

comment:1 by Christian Boos, 8 years ago

Resolution: cantfix
Status: newclosed

WrongTrac? This certainly concerns some plugin, as we don't have #31 in core yet.

comment:2 by matt sable, 8 years ago

Resolution: cantfix
Status: closedreopened

I'm sorry, I think I just wasn't clear enough in my description. This is in regards to something such as

[[TicketQuery(id=123)]]

This patch allows you to include

[[TicketQuery(root=123)]]

which then shows ticket 123 and all it's descendants.

comment:3 by Remy Blank, 8 years ago

Resolution: duplicate
Status: reopenedclosed

That's certainly a valid way to implement ticket hierarchies, but we are aiming at a somewhat more generic solution with #31 and #886, TracDev/Proposals/TicketLinks and TracDev/Proposals/TracRelations. So at this point, we would rather not integrate a limited solution.

comment:4 by Christian Boos, 8 years ago

Right, in plain Trac, you have no notion of descendants… You must be using TH:ChildTicketsPlugin or TH:SubticketsPlugin, or similar. An extension to the core implies the mechanism would useful and adaptable to any plugin.

We referred you to #31, but note also that the more precise ticket for ticket hierarchies is #886, and the SubTickets page. My own current thinking about subtickets (in light of the GenericTrac proposal) is that the ticket id should reflect the hierarchy: a subticket would have an id of e.g. #10231.1, and so on; as a side effect queries for retrieving all tickets in a hierarchy would be trivial…)

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to as closed The owner will be changed from (none) 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.