Page Properties with Horizontal formatting only works if header row at the top of table

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Low
    • None
    • Affects Version/s: 7.4.6, 7.7.4, 7.8.1
    • None
    • 1
    • Severity 2 - Major

      Problem

      Page properties reports don't display the expected results if the table isn't formatted with the header row exactly at the top of the table. Testing on Confluence 7.6.2, this does work, but subsequent versions no longer support this. 

      Environment

      7.7.4, 7.8.1

      Steps to Reproduce

      1. Create a page named Test Page Properties
      2. Add the label tester to the page
      3. Add a page property report macro to the page
      4. Add a table with 3 rows inside the macro, specifying the header on the 2nd row. Should like the image below:

        Report Title: 

        Test Test Space
        1 Test

       

      1. Create a page named Test Page Properties Reports
      2. Add a page property report macro to the page
        1. Set the label to tester
        2. *Leave the *In Space settings as is

      Expected Results

      Page properties report displays the values from row beneath the header row.

      Actual Results

      The values in the Page Properties report are returned either empty or with the formatting set to vertical instead of horizontal. 

      Workaround

      1. Remove the row above the header row from the table containing the page properties. Removing this results in the page properties report displaying the data as expected.
      2. Enable "masterdetail.legacy.parse" dark feature in Confluence. This will result in slower report generation and a hard limit of 1000 rows in the report.

      Notes

      This issue appears to have been introduced in versions after Confluence 7.6.2. The reports work as expected even with the table headers in this version of Confluence. 

              Assignee:
              Unassigned
              Reporter:
              Dante Anthony
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: