Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-36044

JIRA Issue/Filter Macro table column widths are not sizeable

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

      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.

      Workaround

      Reduce the number of columns on the JIRA Issues macro to fit on the page on Confluence without needing to scroll to right.

        1. ss-jira-issue-filter-macro-word.png
          163 kB
          Robert Jacobs
        2. ss-jira-issue-filter-macro-pdf.png
          154 kB
          Robert Jacobs

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

            Hi everyone,

            This is Haibert from the Confluence team. This bug is fixed and I confirmed the functionality to be working as expected. 

            Sincerely,

            Haibert

            Haibert Barfian added a comment - Hi everyone, This is Haibert from the Confluence team. This bug is fixed and I confirmed the functionality to be working as expected.  Sincerely, Haibert

            We have the same issue and I can confirm that removing Change History fixes the issue, BUT "unfortunately", we also need the change history.

            Adnan Vilic added a comment - We have the same issue and I can confirm that removing Change History fixes the issue, BUT "unfortunately", we also need the change history.

            This issue/ bug has been a major issue to our organization. I am working in a a startup and I am trying to bring in a new system and unfortunately Confluence cannot fix this bug. How can I sway my leadership to use confluence if the reports with tables are clunky. please fix this issue or provide a work around. Thanks!

            Aditi Vadodkar added a comment - This issue/ bug has been a major issue to our organization. I am working in a a startup and I am trying to bring in a new system and unfortunately Confluence cannot fix this bug. How can I sway my leadership to use confluence if the reports with tables are clunky. please fix this issue or provide a work around. Thanks!

            We are eperiencing the same problem when texts are long in the Jira issue filter then it is truncated when exporting to pdf Not sure if we are using the change history, but regardless this should be solved or the pdfexport can't be used.

            Tobias Ednersson added a comment - We are eperiencing the same problem when texts are long in the Jira issue filter then it is truncated when exporting to pdf Not sure if we are using the change history, but regardless this should be solved or the pdfexport can't be used.

            elvis added a comment -

            This is definitely a problem and without change history macro. Enough with some Jira description that has a larger image in it like a screenshot

            elvis added a comment - This is definitely a problem and without change history macro. Enough with some Jira description that has a larger image in it like a screenshot

            Nataliia K added a comment -

            Hi e4434f5cc867 and everyone,

            This is Nataliia from the Confluence team. Thank you for raising this bug and bringing it to our attention. After our investigation into this issue, we weren’t able to reproduce the behavior within our instances. We would like to get to the root cause of what you’re experiencing. Could you provide some more details or a screenshot to help us narrow down this case?

            We will keep this issue open for another 14 days, but if we don’t hear back by then we will need to close this out to focus on our upcoming roadmap for all Confluence users.

            Best,

            Nataliia

            Nataliia K added a comment - Hi e4434f5cc867 and everyone, This is Nataliia from the Confluence team. Thank you for raising this bug and bringing it to our attention. After our investigation into this issue, we weren’t able to reproduce the behavior within our instances. We would like to get to the root cause of what you’re experiencing. Could you provide some more details or a screenshot to help us narrow down this case? We will keep this issue open for another 14 days , but if we don’t hear back by then we will need to close this out to focus on our upcoming roadmap for all Confluence users. Best, Nataliia

            This is not a good workaround.... my management is asking for this report/data so should I gob ack to them and say sorry, you can't have it since Confluence can't fit-to-a-page? I'm trying to get management to change over from another system to JIRA/Confluence and this gives them ammunition to stay with the other system... 

            Lillian Shibata-Salley added a comment - This is not a good workaround.... my management is asking for this report/data so should I gob ack to them and say sorry, you can't have it since Confluence can't fit-to-a-page? I'm trying to get management to change over from another system to JIRA/Confluence and this gives them ammunition to stay with the other system... 

            We are having this same issue and do not utilize the Change History Macro on our Confluence spaces so I can't remove it in order to attempt the workaround provided here.   Is there any other workaround that will force the Jira Issue Macro results to wrap?

            Jeffrey Holzapfel added a comment - We are having this same issue and do not utilize the Change History Macro on our Confluence spaces so I can't remove it in order to attempt the workaround provided here.   Is there any other workaround that will force the Jira Issue Macro results to wrap?

              dfe3d5f5e8a2 Haibert Barfian
              e4434f5cc867 Robert Jacobs
              Affected customers:
              23 This affects my team
              Watchers:
              28 Start watching this issue

                Created:
                Updated:
                Resolved: