Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-39021

Page Properties Report Macro Export to Word or PDF only displays 30 results

XMLWordPrintable

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Summary

      Default settings for the Page Properties Report Macro is 30 results if this is extended when exporting to Word or PDF document option is selected only the first 30 results are displayed.

      Steps to Reproduce

      1. Insert Page Properties Report Macro to confluence page
      2. set Number of items to display in advance options to >30 (exe: 31)
      3. Select Export to Word or PDF

      Expected Results

      All results are displayed in exported document

      Actual Results

      Only the first 30 item results are displayed
      Same results if using the Page Export options in Space Tools > Content Tools

      Workaround

      No workaround is available

        1. CONF-39021.doc
          11 kB
        2. TIC-CONF-39021-030416-1343-2.pdf
          12 kB

            [CONFSERVER-39021] Page Properties Report Macro Export to Word or PDF only displays 30 results

            Nguyen Dang added a comment -

            acurth yes, it's all set there, too.

            Nguyen Dang added a comment - acurth yes, it's all set there, too.

            Axel Curth added a comment -

            When will it be fixed in the cloud instance, or is it all set there too?

            Axel Curth added a comment - When will it be fixed in the cloud instance, or is it all set there too?

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment -

            This issue has been resolved in Confluence 5.10.4 which is now available for download.

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment - This issue has been resolved in Confluence 5.10.4 which is now available for download .

            Deleted Account (Inactive) added a comment -

            This is a serious bug and makes Confluence unusable for several use cases! We got complains from several of our customers.
            Please priorities this issue accordingly.

            Deleted Account (Inactive) added a comment - This is a serious bug and makes Confluence unusable for several use cases! We got complains from several of our customers. Please priorities this issue accordingly.

            Alexander Schätzle added a comment - - edited

            Please add Version 5.10.x
            That should be a major bug, because no workaround exists and lot's of users are using especially this functionality!!!
            Can't upgrade to 5.8 or 5.9 until it is not fixed....

            Alexander Schätzle added a comment - - edited Please add Version 5.10.x That should be a major bug, because no workaround exists and lot's of users are using especially this functionality!!! Can't upgrade to 5.8 or 5.9 until it is not fixed....

            Jan-Peter Rusch added a comment -

            Still broken in 5.10.0

            Atlassian, this is NOT a MINOR issue. You've customers who need this macro working asap. We found the bug after upgrading our production system to an affected version. It's 10 month now, some 100s of support calls to our IT. This bug COSTS money. We don't need any new feature, but a WORKING property report macro.

            Jan-Peter

            Jan-Peter Rusch added a comment - Still broken in 5.10.0 Atlassian, this is NOT a MINOR issue. You've customers who need this macro working asap. We found the bug after upgrading our production system to an affected version. It's 10 month now, some 100s of support calls to our IT. This bug COSTS money. We don't need any new feature, but a WORKING property report macro. Jan-Peter

            Melanie Albrecht added a comment -

            I'm seeing the issue here too, on 5.8.9. I don't recall that it was a problem in older releases.

            I use the Page Properties Report macro in lots of places, but the bug does not occur in macros that have been there for a while. I'm seeing it only in the PPR macro that I created today (6 June 2016).

            PPR macros that were last modified on these dates are still working fine: 18 May 2016, 27 April 2016. I am not brave enough to try editing these pages to see what happens.

            Melanie Albrecht added a comment - I'm seeing the issue here too, on 5.8.9. I don't recall that it was a problem in older releases. I use the Page Properties Report macro in lots of places, but the bug does not occur in macros that have been there for a while. I'm seeing it only in the PPR macro that I created today (6 June 2016). PPR macros that were last modified on these dates are still working fine: 18 May 2016, 27 April 2016. I am not brave enough to try editing these pages to see what happens.

            Frank Solutions Atlassian added a comment -

            There's a duplicate issue about this: https://jira.atlassian.com/browse/CONF-40898

            Frank Solutions Atlassian added a comment - There's a duplicate issue about this: https://jira.atlassian.com/browse/CONF-40898

            Frank Solutions Atlassian added a comment -

            Hi there,

            This is a serious bug for me. I've just added 200+ servers to Confluence with the use of this macro, so I could share this information with the company who manages our servers....

            Hope you can fix it soon!

            Vera

            Frank Solutions Atlassian added a comment - Hi there, This is a serious bug for me. I've just added 200+ servers to Confluence with the use of this macro, so I could share this information with the company who manages our servers.... Hope you can fix it soon! Vera

            Michael Corvin added a comment -

            Hi Paul,

            I sure hope that this gets resolved - the page properties macro is incredibly useful as a 'poor man's database' to keep all sorts of data 'single point' defined and link list summaries of it automatically updated. The export to PDF is essential for sharing the summary tables with teammates or customers who don't have wiki access, so this bug is a real pain!

            I've used it for things such as a simple requirements database with different summary tables showing subsets of the requirement properties (e.g verification status). I combine it with the 'Page Excerpt' macro so that I can insert requirement reference and verification assertion into test procedures as an excerpt, linked back to the requirement page, rather than by cut/paste...

            I haven't checked if anyone has put in the feature request to make the page property summary macro able to use multiple labels - or even better, a simple regex for selecting one or more labels.

            cheers, Mike

            Michael Corvin added a comment - Hi Paul, I sure hope that this gets resolved - the page properties macro is incredibly useful as a 'poor man's database' to keep all sorts of data 'single point' defined and link list summaries of it automatically updated. The export to PDF is essential for sharing the summary tables with teammates or customers who don't have wiki access, so this bug is a real pain! I've used it for things such as a simple requirements database with different summary tables showing subsets of the requirement properties (e.g verification status). I combine it with the 'Page Excerpt' macro so that I can insert requirement reference and verification assertion into test procedures as an excerpt, linked back to the requirement page, rather than by cut/paste... I haven't checked if anyone has put in the feature request to make the page property summary macro able to use multiple labels - or even better, a simple regex for selecting one or more labels. cheers, Mike

              ndang Nguyen Dang
              emccutcheon Earl McCutcheon
              Affected customers:
              33 This affects my team
              Watchers:
              37 Start watching this issue

                Created:
                Updated:
                Resolved: