Opened 10 years ago
Last modified 2 years ago
#11702 new enhancement
Add a macro for listing ticket Components
| Reported by: | Ryan J Ollos | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-releases |
| Component: | ticket system | Version: | |
| Severity: | normal | Keywords: | component bitesized |
| Cc: | walty8@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
As discussed in comment:9:ticket:1233, it would be nice to have a macro for listing ticket system Components. comment:25:ticket:1233 suggests having a link to the query page from an open tickets column generated by the macro.
The TicketQuery macro might be the most similar in term of existing macros, given its output formats that we might want to pattern after.
Macros for Milestones, Versions and Ticket enums might follow after this one. A macro for listing ticket enums could be used on the TracTicketTriage#StatusandResolution page.
The macro would be useful on the TracTicketTriage, where we currently do not list the components.
Addition of this macro would deprecate ComponentsProcessorMacro.
Attachments (0)
Change History (14)
comment:1 by , 10 years ago
| Status: | new → assigned |
|---|
comment:2 by , 10 years ago
| Milestone: | 1.1.3 → next-dev-1.1.x |
|---|---|
| Owner: | removed |
| Status: | assigned → new |
comment:3 by , 10 years ago
| Keywords: | bitesized added |
|---|
comment:4 by , 9 years ago
comment:5 by , 9 years ago
| Cc: | added |
|---|
comment:6 by , 9 years ago
Well, the macro could support a few different output formats (specified with the format parameter), like TicketQuery or other WikiMacros do. Typical values are compact, list, table. Adding a query link or not could be controlled by a querylink flag (or parameter specifying the query itself).
comment:7 by , 9 years ago
| Description: | modified (diff) |
|---|
comment:8 by , 9 years ago
| Milestone: | next-dev-1.1.x → next-dev-1.3.x |
|---|
Narrowing focus for milestone:1.2. Please move ticket to milestone:1.2 if you intend to fix it.
comment:9 by , 8 years ago
| Description: | modified (diff) |
|---|
comment:10 by , 7 years ago
A milestone macro could be used at TracDev/ReleaseTesting, so that the page wouldn't need to be updated on every release.
comment:11 by , 7 years ago
We might be able to use the following even if no enhancement.
[[TicketQuery(group=milestone,keywords=release,status!=closed,format=compact)]] ---- [[TicketQuery(group=milestone,keywords=release,status!=closed)]]
No results
No results
comment:12 by , 7 years ago
That looks good, thanks. Edited TracDev/ReleaseTesting@100 and TracDev/ReleaseChecklist@119.
comment:14 by , 5 years ago
| Milestone: | next-dev-1.5.x → next-major-releases |
|---|
I carefully read the two comments, as well as the description of this ticket for a couple of times, yet I could not fully understand the requirements.
in comment:9:ticket:1233,
rblankwant a macro that generate something like[[TracIni]], which I believe should be a list of tables. So I guess the expected outcome should be each table contains the description for one component?in comment:25:ticket:1233,
cbooswant an extra column, inside the table generated by the macro. The extra column contains a link calledopen tickets(or I believe should actually beopened ticket), which link to the query page of tickets for that component.however, in this ticket, the layout is expected to be something like
[[TicketQuery()]], the output of which is actually a list of items (ticket number & ticket description), without any tables and columns as far as I see.I am sorry for my poor understanding, may I know what's the expected UI for this one please? If there is a simple screen mock up, it would really great.
thanks.