Add a macro for listing ticket Components

[Ryan J Ollos]

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 and Versions might follow after this one.

The macro would be useful on the TracTicketTriage, where we currently do not list the components.

Addition of this macro would deprecate ​ComponentsProcessorMacro.

[walty <walty8@…>]

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, rblank want 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, cboos want an extra column, inside the table generated by the macro. The extra column contains a link called open tickets (or I believe should actually be opened 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.

[Christian Boos]

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).