#6523 closed enhancement (duplicate)
[TicketQuery] with reports
| Reported by: | Markus.Staab | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | query system | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Would be nice to output the tickets of a report with the TicketQuery macro
Attachments (0)
Change History (10)
comment:1 by , 17 years ago
comment:3 by , 17 years ago
| Milestone: | → 2.0 |
|---|---|
| Owner: | removed |
Sounds useful indeed. A working patch would speed up the integration of this feature :-)
follow-up: 10 comment:6 by , 13 years ago
| Component: | general → query system |
|---|
I would need this functionality also. I have a report to list tickets from the latest/most recent milestone (actual Sprint backlog), which I resolve in SQL with a subselect on milestones, ORDER BY <milestone-date> DESC LIMIT 1. This can as of now not be done with TracQuery Syntax, so I cannot report on tickets from e.g. the actual backlog with the TicketQuery Macro without having to change multitudes of hard references to milestones in my reporting overview whenever I start a new Sprint.
It works with TicketBoxMacro (e.g. [[TicketBox([report:1])]], maybe some inspiration can derive therefrom), but TBM does not give me table output like TicketQuery Macro does.
So it would definitely be helpful to have something like [[TicketQuery(report=9,table)]], despite the plans to abandon SQL reports at all (plans I do not endorse unless TracQueries give me everything I can do with SQL, btw.)
comment:9 by , 8 years ago
| Milestone: | unscheduled |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Duplicate of #12810. See also th:WikiReportMacro.
comment:10 by , 8 years ago
Replying to kontakt at meitzner dot net:
So it would definitely be helpful to have something like
[[TicketQuery(report=9,table)]], despite the plans to abandon SQL reports at all (plans I do not endorse unless TracQueries give me everything I can do with SQL, btw.)
Unlikely that TracReports will be abandoned. See also #12786.



+1 This would be very useful!