Werk #20018: Section numbers in PDF reports no longer skip after un-numbered headings
| Component | Reporting & availability | ||||||
| Title | Section numbers in PDF reports no longer skip after un-numbered headings | ||||||
| Date | Jun 4, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
What changed
Section numbers in generated PDF reports are now correct when a report element renders an un-numbered sub-heading before a numbered one.
Why this matters
Several report elements render sub-headings that carry no number of their own. For example, a "GUI view" element that groups its rows prints a group header (a date or host name), and an availability element prints "Timeline of ..." and "Annotations" sub-headings. Previously each of these silently consumed a section number, so the next numbered heading at that level skipped one.
In practice you would see numbering like "1.2" where you expected "1.1" after a grouped view, or "3.2" instead of "3.1" after an availability timeline. The numbers were internally consistent but looked wrong and made the report - and its table of contents - harder to follow.
Un-numbered sub-headings no longer take up a number, so numbering stays sequential.