#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: | |||
| Internal 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)
Change History (5)
by , 14 years ago
| Attachment: | root_patch_file.diff added |
|---|
comment:1 by , 14 years ago
| Resolution: | → cantfix |
|---|---|
| Status: | new → closed |
comment:2 by , 14 years ago
| Resolution: | cantfix |
|---|---|
| Status: | closed → reopened |
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 , 14 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | reopened → closed |
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 , 14 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…)
Patch