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

Page Export to PDF with JIRA Issue Macro showing "Getting issue details"

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

      Summary

      Page Export to PDF with JIRA Issue Macro showing "Getting issue details"

      Steps to Reproduce

      1. Create a page with JIRA Issue Macro. Make sure the macro displays the result on the page
      2. Export to PDF

      Expected Results

      Page exported with the macro displaying the JIRA issue number,summary and status

      Actual Results

      Page exported with the macro displaying the JIRA issue number, Getting issue details... and the word "Status"

      Notes

      Sample of PDF output

      Workarounds

      (Submitted by a customer in the comments, but the workarounds below have been validated)

      1. Using account with Confluence Administrator role to export the PDF
      2. When using the 'Table of Content' macro; disable the 'Printable' option - TOC will not be displayed when your Confluence-page is exported in PDF;
      3. Use 'Table of Content' macro only at the end of a Confluence-page, after all your JIRA-links are mentioned on the impacted Confluence-page;
      4. Do not use 'Table Of Content'-macro the impacted Confluence-page;
      5. Exporting the Confluence page to PDF via the internal print functionality ('export to PDF') in the browser.

            [CONFSERVER-39519] Page Export to PDF with JIRA Issue Macro showing "Getting issue details"

            vera.diaz added a comment -

            I need a solution to this issue. I need the Jira information and table of contents in my PDF. 

            vera.diaz added a comment - I need a solution to this issue. I need the Jira information and table of contents in my PDF. 

            Chas Frick added a comment -

            I have a solution that worked for me using Confluence 7.19.1 and allowed me to export things and use a Table of Contents (TOC)

            • Insert the TOC wherever you want it on the page
            • Insert a "Page properties" macro anywhere on the page above the TOC macro
            • Set the "Page properties" to be hidden
            • Copy/Paste the URL of any of the Jira issue you want to link into the "Page properties" macro
            • Publish your page and now the Jira issues should all show up with proper status when exporting to PDF!
            • Go into Jira and remove the linked confluence page if you don't want it linked

            Hopefully that workaround helps you out! 

            Chas Frick added a comment - I have a solution that worked for me using Confluence 7.19.1 and allowed me to export things and use a Table of Contents (TOC) Insert the TOC wherever you want it on the page Insert a "Page properties" macro anywhere on the page above the TOC macro Set the "Page properties" to be hidden Copy/Paste the URL of any of the Jira issue you want to link into the "Page properties" macro Publish your page and now the Jira issues should all show up with proper status when exporting to PDF! Go into Jira and remove the linked confluence page if you don't want it linked Hopefully that workaround helps you out! 

            steff added a comment -

            this annoying Issue is still here in Confluence 8.9.1...

             

            steff added a comment - this annoying Issue is still here in Confluence 8.9.1...  

            Volker Otto added a comment - - edited

            This is a really annoying issue. We can build great summary pages with Jira links in confluence, but exporting them for the customer really looks broken. This needs to be fixed at least for the Jira ticket integration.

            Showing the real title and status should be possible.

            Volker Otto added a comment - - edited This is a really annoying issue. We can build great summary pages with Jira links in confluence, but exporting them for the customer really looks broken. This needs to be fixed at least for the Jira ticket integration. Showing the real title and status should be possible.

            This issue persists in Confluence 8.0.2

            harmen_moll added a comment - This issue persists in Confluence 8.0.2

            MRANJ added a comment -

            Confluence version 7.13.7 is also impacted with this bug.

            MRANJ added a comment - Confluence version 7.13.7 is also impacted with this bug.

            This issue is driving our teams (and management, who relies on PDF reports since they don't want to log into Jira or Confluence) nuts.

            None of the workarounds except item 5 are useful.  Printing the webpage from Confluence often has semi-transparent blocks at the start of some pages or covering sections, negating its' use as an effective workaround.  

             

            Seems that this should be an easy fix - why Long Term Backlog?  (i.e. freezer, might as well be honest and say "won't fix"). 

             

            Just get it fixed, can't be longer than a day or two for a developer.  Seems the PDF engine just needs to look at the links and wait for a transition for each for anything OTHER than "Getting issue details"

             

             

            Peter Saulesleja added a comment - This issue is driving our teams (and management, who relies on PDF reports since they don't want to log into Jira or Confluence) nuts. None of the workarounds except item 5 are useful.  Printing the webpage from Confluence often has semi-transparent blocks at the start of some pages or covering sections, negating its' use as an effective workaround.     Seems that this should be an easy fix - why Long Term Backlog?  (i.e. freezer, might as well be honest and say "won't fix").    Just get it fixed, can't be longer than a day or two for a developer.  Seems the PDF engine just needs to look at the links and wait for a transition for each for anything OTHER than " Getting issue details"    

            Version 7.1.2 is affected, too.

            One or two words about the suggested Workarounds:

            1. Using account with Confluence Administrator role to export the PDF => For a general user it is useless.
            2. When using the 'Table of Content' macro; disable the 'Printable' option - TOC will not be displayed when your Confluence-page is exported in PDF; => If if export a page I usualy want the whole page, with the  'Table of content'
            3. Use 'Table of Content' macro only at the end of a Confluence-page, after all your JIRA-links are mentioned on the impacted Confluence-page; => at the end of a page, the TOC is useless. I need it in the beginning, to not having to scroll the whole page down... if I am at the end, I already have scrolled it all dwn...
            4. Do not use 'Table Of Content'-macro the impacted Confluence-page; => that is a poor suggestion
            5. Exporting the Confluence page to PDF via the internal print functionality ('export to PDF') in the browser. => that is a poor suggestion, too

            Paula Dasch added a comment - Version 7.1.2 is affected, too. One or two words about the suggested Workarounds: Using account with Confluence Administrator role to export the PDF => For a general user it is useless. When using the 'Table of Content' macro; disable the 'Printable' option - TOC will not be displayed when your Confluence-page is exported in PDF; => If if export a page I usualy want the whole page, with the  'Table of content' Use 'Table of Content' macro only at the end of a Confluence-page, after all your JIRA-links are mentioned on the impacted Confluence-page; => at the end of a page, the TOC is useless. I need it in the beginning, to not having to scroll the whole page down... if I am at the end, I already have scrolled it all dwn... Do not use 'Table Of Content'-macro the impacted Confluence-page; => that is a poor suggestion Exporting the Confluence page to PDF via the internal print functionality ('export to PDF') in the browser. => that is a poor suggestion, too

            This stopped working altogether, regardless of the presence of a Table of Contents macro on the page....

            LONG TERM BACKLOG = will never fix ?

            Stefan Anghel added a comment - This stopped working altogether, regardless of the presence of a Table of Contents macro on the page.... LONG TERM BACKLOG = will never fix ?

            Also in 6.15.x

            Mark de Bont [Terberg] added a comment - Also in 6.15.x

            Oleg Gerasymchuk added a comment - - edited

            Dear Atlassian Support Team.

            Issue still appear in Confluence 6.11.1

            Last time this issue updated about a year ago, and it's still unassigned.

            Could you please share your plans about fixing this issue?

            I want to add also: I can't reproduce issue when using account with Confluence Administrator role. Not sure if it's related, but maybe this info will be useful for troubleshooting.

            Regards,

            Oleg Gerasymchuk added a comment - - edited Dear Atlassian Support Team. Issue still appear in Confluence 6.11.1 Last time this issue updated about a year ago, and it's still unassigned. Could you please share your plans about fixing this issue? I want to add also: I can't reproduce issue when using account with Confluence Administrator role. Not sure if it's related, but maybe this info will be useful for troubleshooting. Regards,

            Confirmed Table Of Content macro affecting the issue, once remove Table of Content macro, the generated PDF could show correct Jira marco name and status.

            My Confluence version is 6.9.0

            Yan Kai Pong Francis added a comment - Confirmed Table Of Content macro affecting the issue, once remove Table of Content macro, the generated PDF could show correct Jira marco name and status. My Confluence version is 6.9.0

            Hi Community,

            I would like to report some workarounds that I have tested, but these are not mentioned in the report itself:

            1) When using the 'Table of Content' macro; disable the 'Printable' option - TOC will not be displayed when your Confluence-page is exported in PDF;

            2) Use 'Table of Content' macro only at the end of a Confluence-page, after all your JIRA-links are mentioned on the impacted Confluence-page;

            3) Do not use 'Table Of Content'-macro the impacted Confluence-page;

            4) Exporting the Confluence page to PDF via the internal print functionality ('export to PDF') in the browser.

            5) I experimented with 'Table of Contents Zone'-macro; was not correctly available in the environment of my client. I think this could be a good workaround.

            Kind regards,

            Stijn Adams
            DevOps Engineer at Evolane, powered by CalmWare

            Deleted Account (Inactive) added a comment - Hi Community, I would like to report some workarounds that I have tested, but these are not mentioned in the report itself: 1) When using the 'Table of Content' macro; disable the 'Printable' option - TOC will not be displayed when your Confluence-page is exported in PDF; 2) Use 'Table of Content' macro only at the end of a Confluence-page, after all your JIRA-links are mentioned on the impacted Confluence-page; 3) Do not use 'Table Of Content'-macro the impacted Confluence-page; 4) Exporting the Confluence page to PDF via the internal print functionality ('export to PDF') in the browser. 5) I experimented with 'Table of Contents Zone'-macro; was not correctly available in the environment of my client. I think this could be a good workaround. Kind regards, Stijn Adams DevOps Engineer at Evolane, powered by CalmWare

            Wolf Wolfer added a comment - - edited

            As a workaround you can use the macro "Table of content zone" instead of plain "toc".

            Tested and works fine for Confluence 5.10.4

            Wolf Wolfer added a comment - - edited As a workaround you can use the macro "Table of content zone" instead of plain "toc". Tested and works fine for Confluence 5.10.4

            Please fix

            Connor McCarty added a comment - Please fix

            Still happening in Confluence 6.3.1

            sdeken-tpsg added a comment - Still happening in Confluence 6.3.1

            A Denis added a comment -

            This also happens on Confluence 6.1.0

            A Denis added a comment - This also happens on Confluence 6.1.0

            I've forgotten it

            This is ridiculous !!!

            Since 2015 this is a known bug and atlassian does not fix it. What is your focus since then?

            And how the other customers already told you this affects the version 6 as well, so why dont update this issue regaring the affected version?

            And above all, why dont you fix it?

            Antonio D'Errico added a comment - I've forgotten it This is ridiculous !!! Since 2015 this is a known bug and atlassian does not fix it. What is your focus since then? And how the other customers already told you this affects the version 6 as well, so why dont update this issue regaring the affected version? And above all, why dont you fix it?

            Hello,

            we have the same problem. this issue occurs when a toc is added to the page.

            we removed the toc from the page and export the page to pdf was succesfully.

             

            best regards

            toni

            Antonio D'Errico added a comment - Hello, we have the same problem. this issue occurs when a toc is added to the page. we removed the toc from the page and export the page to pdf was succesfully.   best regards toni

            Same issue here with JIRA v7.1.2 and Confluence v6.0.4

            Josef Freundorfer added a comment - Same issue here with JIRA v7.1.2 and Confluence v6.0.4

            We are affected by this as well with Confluence 5.10.8 and JIRA 6.4.12. Looks like the report just needs more time before taking the pdf. Anyone know of a timeout we could adjust?

            Brian KimJohnson added a comment - We are affected by this as well with Confluence 5.10.8 and JIRA 6.4.12. Looks like the report just needs more time before taking the pdf. Anyone know of a timeout we could adjust?

            KPSA added a comment -

            We're on 5.10.3 and JIRA 7.1.9. Sadly, however, Jason's workaround didn't work here. We get the same broken export.

            KPSA added a comment - We're on 5.10.3 and JIRA 7.1.9. Sadly, however, Jason's workaround didn't work here. We get the same broken export.

            Hello,

            same issue for us too. Confluence 5.10.2 and Jira 6.2.

            The workaround suggested by Jason also works for us, but is not realy practicable for our users...

            Regards
            Josef

            afbp Application Services AG added a comment - Hello, same issue for us too. Confluence 5.10.2 and Jira 6.2. The workaround suggested by Jason also works for us, but is not realy practicable for our users... Regards Josef

            RiccardoR added a comment -

            Hello,

            same issue for us. Confluence 5.9.10, Jira 7.1.1.

            The workaround suggested by Jason also works for us.

            Regards,
            Riccardo Serafin.

            RiccardoR added a comment - Hello, same issue for us. Confluence 5.9.10, Jira 7.1.1. The workaround suggested by Jason also works for us. Regards, Riccardo Serafin.

            To update, we have found a work around for this issue by using the; Space Tools > Export > PDF > Custom Export tool and limiting to specific page for export, rather than using the page export PDF utility.

            Jason Asker added a comment - To update, we have found a work around for this issue by using the; Space Tools > Export > PDF > Custom Export tool and limiting to specific page for export, rather than using the page export PDF utility.

            Hello,
            We are now experiencing the same issue as described after update of JIRA from 6.4.3 to 7.0.4 (Software) and Confluence from 5.7.3 to 5.9.2.
            Any update on a potential workaround, or when this issue is likely to be fixed?

            Regards,
            Jason Asker

            Jason Asker added a comment - Hello, We are now experiencing the same issue as described after update of JIRA from 6.4.3 to 7.0.4 (Software) and Confluence from 5.7.3 to 5.9.2. Any update on a potential workaround, or when this issue is likely to be fixed? Regards, Jason Asker

              Unassigned Unassigned
              nmohdkhalid Nabil
              Affected customers:
              92 This affects my team
              Watchers:
              85 Start watching this issue

                Created:
                Updated: