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

Jira issue filter macro does not preserve custom columns when edited

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 7.4.7, 7.13.0, 7.18.1, 7.19.4
    • Macros - Jira Macros
    • None

      Issue Summary

      After Confluence is upgraded, previously added custom columns added in Jira issue macro are lost when the Jira issue macro is edited in the upgraded version of Confluence.

      Steps to Reproduce

      1. Create a Jira Issue Macro in Confluence 7.0.4
      2. Search for an issue key (e.g. project = "TEST")
      3. Expand Display Options and select table and also add a custom column such as Fix Version/s
      4. Upgrade Confluence to say Confluence 7.13.2
      5. Reload the previous page with Jira issue macro. The page will still show the Jira Issue Macro with Fix Version/s column
      6. Edit the page and edit the Jira Issue macro. Press Insert on Jira issue macro
      7. Publish the page

      Expected Results

      Custom columns that were previously added in the older Confluence version should still be displayed

      Actual Results

      Custom columns that were previously added in the older Confluence version are lost

      Workaround

      Deleting the existing macros present prior to upgrading, and re-adding them should help with this behavior.

            [CONFSERVER-64235] Jira issue filter macro does not preserve custom columns when edited

            Hi

            this bug seems to be recurring and is now impacting my production environment. Has anyone else reported this recently please?

            Deleted Account (Inactive) added a comment - Hi this bug seems to be recurring and is now impacting my production environment. Has anyone else reported this recently please?

            This is impacting our BA team, please inform if it will be fixed or there is 0plan to fix it

            Jyoti Singh added a comment - This is impacting our BA team, please inform if it will be fixed or there is 0plan to fix it

            Hi Everyone,  This is affecting our team.  The workaround is they have to delete the entire Jira filter macro.  Then re-add it, re-set the columns.   In the code you can actually see that this version of Confluence is pulling based on "ColumnIds=" vs "Columns=" for selecting the columns.  I don't even see how one fixes it, other than regress the code back to Columns. 

             

            Susan Hauth [Jira Queen] added a comment - Hi Everyone,  This is affecting our team.  The workaround is they have to delete the entire Jira filter macro.  Then re-add it, re-set the columns.   In the code you can actually see that this version of Confluence is pulling based on "ColumnIds=" vs "Columns=" for selecting the columns.  I don't even see how one fixes it, other than regress the code back to Columns.   

            Hi Team

            can you update on this.

            at least an ETA or if this issue will be resolved in released latest versions.

            Manjunath R added a comment - Hi Team can you update on this. at least an ETA or if this issue will be resolved in released latest versions.

            Hi Team

            Kindly provide an update here

            Manjunath R added a comment - Hi Team Kindly provide an update here

            Hi Team

             

            We need a solution for this issue 

            kindly provide a fix ASAP.

            Manjunath R added a comment - Hi Team   We need a solution for this issue  kindly provide a fix ASAP.

            Hi Team,

             

            Is this issue fixed in latest versions 7.13.1 or 7.14.0?

            Please let us know

            Manjunath R added a comment - Hi Team,   Is this issue fixed in latest versions 7.13.1 or 7.14.0? Please let us know

            Hi Team

            This is impacting our PROD

            Kindly provide an update here

             

            Manjunath R added a comment - Hi Team This is impacting our PROD Kindly provide an update here  

              Unassigned Unassigned
              dhowell@atlassian.com Derek Howell
              Affected customers:
              8 This affects my team
              Watchers:
              18 Start watching this issue

                Created:
                Updated: