Report rendering needs some general overhaul

[Carsten Klein <carsten.klein@…>]

When using column_ for breaking the row after the column, everything works fine except that the column has no colspan assigned to extend it across the columns left available to the right.

E.g.

select id, summary as summary_, component, milestone from ticket…

will render both the id and the summary in one line and the rest in the following line.

However, the summary column will only be one column wide whereas it should extend across the available N-1 columns to the right.

[Remy Blank]

The {row}_ syntax only introduces a line break, not a full line. You're probably looking for the _{row}_ syntax instead. Try:

select id, component, milestone, summary as _summary_ from ticket...

See TracReports for more details.

[carsten.klein@…]

I sure know that it is working, but it would be nicer to have it extend across the remaining columns.

I am currently looking into a patch that would remedy the situation, however, it renders quite complicated to make it work (hidden columns etc.).

I will reopen this as a enhancement request and put it on low.

[Carsten Klein <carsten.klein@…>]

patch to both report.py and templates/report_view.py

[Carsten Klein <carsten.klein@…>]

the presented patch remedies the situation that

• under certain conditions empty table rows are being rendered (e.g. id as _ticket_ as the second column after … as color or inbetween)
• all columns that are considered fullrows will now extend not to a standard of 100 columns but to the actual number of available (visible) columns
• all columns that cause a row break will now also extend across the remainder of the columns to the right
• each row in a row_group will be in a separate table body (discussable)

all in all this should provide for nicer renderings of ticket reports

[Carsten Klein <carsten.klein@…>]

Replying to Carsten Klein <carsten.klein@…>:

additionally

• outcommented the <hr> in case of a fullrow
• fullrow cells will now have the correct class name, e.g. summary and not fullrow

[Remy Blank]

Thanks for the patch.

[Carsten Klein <carsten.klein@…>]

revised patch to report.py

[Carsten Klein <carsten.klein@…>]

the previous patch to report.py rendered the view unusable (i.e. it missed inclusion of ticket id when id was rendered as a fullrow, e.g. id as _ticket_),

[Carsten Klein <carsten.klein@…>]

possible regression here still: user does not include ticket.id in query

result would be that all tickets in the report will not be navigateable.

perhaps we should introduce the ticket id as a mandatory requirement for reports?