Jira issue filter macro does not preserve custom columns when edited

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 7.4.7, 7.13.0, 7.18.1, 7.19.4
    • Component/s: Macros - Jira Macros
    • None
    • 13
    • Severity 3 - Minor
    • 1

      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.

            Assignee:
            Unassigned
            Reporter:
            Derek Howell
            Votes:
            8 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated: