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

JIRA Issues Macro filter behaviour has changed so that it no longer saves the filter, but rather hard-codes the results.

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      The problem

      Inserting a URL to a saved filter, eg http://localhost:9604/browse/TEST-3?filter=10000 autocompletes to the JQL content of the filter - 'description ~ "description"' in my test case - so when filter 10000 changes, the JIRA Issues will still be 'description ~ "description"'. This is not the same as previous behaviour, where the filter would remain in the macro and changes to the filter would be reflected in Confluence.

      Steps to Reproduce

      1. Create and view a filter in JIRA
      2. Copy the URL
      3. Create a JIRA Issues Macro in Confluence 5.2.3
      4. Paste the URL into the macro
        • Observe that the URL is immediately changed to the JQL of the filter.
      5. Save the JIRA Issues Macro
      6. Change the filter in JIRA so that the results are different
      7. Reload the Confluence page
        • Observe that the results do not reflect the changes to the filter

            [CONFSERVER-30428] JIRA Issues Macro filter behaviour has changed so that it no longer saves the filter, but rather hard-codes the results.

            @Denise Thanks for the update and clarification.

            Stefan Hett added a comment - @Denise Thanks for the update and clarification.

            stefan22, apologies for not updating the Confluence Server version in this ticket. The issue was fixed in JIRA Issues Macro 5.1.2. Confluence 5.3.2 was the first version to contain this fix automatically, as it bundled JIRA Issues Macro 5.1.3. However, any version of Confluence that is compatible with JIRA Issues Macro 5.1.2, eg Confluence 5.2.3, can update the plugin and receive the fix.

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment - stefan22 , apologies for not updating the Confluence Server version in this ticket. The issue was fixed in JIRA Issues Macro 5.1.2. Confluence 5.3.2 was the first version to contain this fix automatically, as it bundled JIRA Issues Macro 5.1.3. However, any version of Confluence that is compatible with JIRA Issues Macro 5.1.2, eg Confluence 5.2.3, can update the plugin and receive the fix.

            Running Confluence 5.2.3 with JIRA Macros 5.1.3 the issue cannot be reproduced here. Hence assuming this was also fixed for non OD installations and presumably also in a JIRA Macros release between the version shipped with 5.2.3 and 5.1.3.

            Stefan Hett added a comment - Running Confluence 5.2.3 with JIRA Macros 5.1.3 the issue cannot be reproduced here. Hence assuming this was also fixed for non OD installations and presumably also in a JIRA Macros release between the version shipped with 5.2.3 and 5.1.3.

            Anatoli added a comment - - edited

            tvu, I agree.

            Anatoli added a comment - - edited tvu , I agree.

            TruongA added a comment - - edited

            akazatchkov: To fix this case, when user paste URL of filter, we should auto-convert to JQL as "filter = 'Filter Name'" and NO need to retrieve the real JQL of filter. What do you think?

            TruongA added a comment - - edited akazatchkov : To fix this case, when user paste URL of filter, we should auto-convert to JQL as "filter = 'Filter Name'" and NO need to retrieve the real JQL of filter. What do you think?

              dtran@atlassian.com Duy Quoc Tran (Inactive)
              dunterwurzacher Denise Unterwurzacher [Atlassian] (Inactive)
              Votes:
              14 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: