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

      Summary
      When I insert a JIRA Issue/Filter macro on a Confluence page as a table, a long text is not wrapped and the width of the column is fixed by the length of the text.
      If the the page is then exported to Word or PDF, the table either runs off the page (Word) or columns are missing entirely (PDF).

      Update: The Change History macro is causing this issue. After removing the Change History macro from the Confluence page, the text is wrapping as expected and all the table columns I have defined are visible on the page even after exporting to Word and PDF formats.

      Note: Depending on the number of columns defined,JIRA Issue/Filter Macro tables are prone to overflow the page when exported.

      Steps to Reproduce:

      1. Add the Jira Issues macro to a page. Include a field in the configuration that contains a long text description.
      2. Save the page and note that the text does wrap correctly. 
      3. Edit the page again. Add the Change History macro to the page and save.

      Expected Results:
      The text wrapping will correctly render on the page. 

      Actual Results:
      The word wrapping is removed from the issues macro and you have to scroll horizontally to read the text. 

            [CONFSERVER-36044] JIRA Issue/Filter Macro table column widths are not sizeable

            REUK IT added a comment -

            For us we believe the Change History Macro is at fault, when exporting to PDF (using Scroll PDF), it is only the columns that relate to Change History that do not wrap the text and are exported as a continuous line.  We have confirmed with K15t (authors of Scroll PDF) that the Change History Macro is the cause of the issue we are experiencing.

            REUK IT added a comment - For us we believe the Change History Macro is at fault, when exporting to PDF (using Scroll PDF), it is only the columns that relate to Change History that do not wrap the text and are exported as a continuous line.  We have confirmed with K15t (authors of Scroll PDF) that the Change History Macro is the cause of the issue we are experiencing.

            We are experiencing the same issue, but the Change History macro has not been added to the page so this cannot be the culprit. 

            Lydia Strebe added a comment - We are experiencing the same issue, but the Change History macro has not been added to the page so this cannot be the culprit. 

            Paul Beck added a comment -

            Change History Macro is the culprit I've confirmed.  This macro is needed for export compliance purposes on our confluence pages.

            Paul Beck added a comment - Change History Macro is the culprit I've confirmed.  This macro is needed for export compliance purposes on our confluence pages.

            If there is code you cold provide as a workaround on our side we'd be open to that as well.  Thanks.

            Matthew Zach added a comment - If there is code you cold provide as a workaround on our side we'd be open to that as well.  Thanks.

            What Louise said.

            Matthew Zach added a comment - What Louise said.

              Unassigned Unassigned
              e4434f5cc867 Robert Jacobs
              Affected customers:
              29 This affects my team
              Watchers:
              27 Start watching this issue

                Created:
                Updated: