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

JIRA issue macro aggressively caches, new issues take a while to appear in the issues macro

XMLWordPrintable

    • 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 new JIRA Issue macro, accessible via Insert > JIRA Issue, does not allow the user the configure caching. Currently it's always on. The problem here is that with caching always enabled, the information shown in Confluence is not always up-to-date.

      Steps to reproduce

      1. In JIRA, create a project with a key of TEST
      2. Create one issue under TEST
      3. On the Confluence editor, use Insert > JIRA Issue, and set the JQL to "project=TEST". Save the macro and page. One issue is shown
      4. Create another issue under TEST
      5. Refresh the Confluence page. The second issue does not appear until the cache is expired, or if it's flushed manually via Confluence Admin > Cache Statistics

      A workaround solution, You can remove the cache by following steps:

      1. Go to the page "Confluence Admin >> Cache Statistics >> Advanced"
      2. Search for the term "JIRA Issues".
      3. Change the value from "100" (default) to "1"
      4. Click the button "Adjust Size" to enable the change.

      Other issues

      This is a related but separate issue from CONF-22845, which addresses the original JIRA Issues macro.

            [CONFSERVER-30077] JIRA issue macro aggressively caches, new issues take a while to appear in the issues macro

            Andy Hurley added a comment -

            Not really had this before but since upgrading to Jira 8.5 (Confluence on 6.13) we have seen this get a lot worse. Users complain that their issues are not being shown in realtime but I think it boils down to this problem. The items update when the refresh is used on the macro.

            Andy Hurley added a comment - Not really had this before but since upgrading to Jira 8.5 (Confluence on 6.13) we have seen this get a lot worse. Users complain that their issues are not being shown in realtime but I think it boils down to this problem. The items update when the refresh is used on the macro.

            John Klenk added a comment -

            My company is using Confluence 6.10.2, and this problem still happens.

            So when viewing a Jira query macro on a Confluence page, tickets that should be included/excluded may not be, and the content of the various fields will not be current (so you may be seeing an old description, summary, status, etc...).  To work around this, I have to wait 5-10 minutes and reload the page, or click the Refresh link for every query on every page.  Of course most people would expect to do that, so it causes lots of confusion and wasted time.

            Is there any way to get somebody from Atlassian to take another look at this?  Thanks!

            John Klenk added a comment - My company is using Confluence 6.10.2, and this problem still happens. So when viewing a Jira query macro on a Confluence page, tickets that should be included/excluded may not be, and the content of the various fields will not be current (so you may be seeing an old description, summary, status, etc...).  To work around this, I have to wait 5-10 minutes and reload the page, or click the Refresh link for every query on every page.  Of course most people would expect to do that, so it causes lots of confusion and wasted time. Is there any way to get somebody from Atlassian to take another look at this?  Thanks!

            Deleted Account (Inactive) added a comment -

            I am having a similar problem with my custom Confluence Macro. Can you please explain what the solution was so I can implement it on my custom macro code? 

            Deleted Account (Inactive) added a comment - I am having a similar problem with my custom Confluence Macro. Can you please explain what the solution was so I can implement it on my custom macro code? 

            Nguyen Dang added a comment - - edited

            kanderson1, I assume you're mentioning JIRA Issues Macro (JIM), and not JIRA gadgets. Currently it displays data based on jql, so if you insert a jql such as "status = open" in JIM and save the page, then go to JIRA and sort by key, the jql in JIRA will be updated to "status = open ORDER BY key" but the jql in Confluence stays the same.

            To overcome this problem, you can update JIM with your new "status = open ORDER BY key". There is an up coming feature https://jira.atlassian.com/browse/CONF-30114 that will let you sort the issue table directly in Confluence when viewing a page.

            Nguyen Dang added a comment - - edited kanderson1 , I assume you're mentioning JIRA Issues Macro (JIM) , and not JIRA gadgets . Currently it displays data based on jql, so if you insert a jql such as "status = open" in JIM and save the page, then go to JIRA and sort by key, the jql in JIRA will be updated to "status = open ORDER BY key" but the jql in Confluence stays the same. To overcome this problem, you can update JIM with your new "status = open ORDER BY key". There is an up coming feature https://jira.atlassian.com/browse/CONF-30114 that will let you sort the issue table directly in Confluence when viewing a page.

            kimberly anderson added a comment -

            Is this related to the sort order not working on the jira issues gadget?
            I logged the issue here and it is not working using the onDemand version.
            https://support.atlassian.com/browse/JST-83757

            kimberly anderson added a comment - Is this related to the sort order not working on the jira issues gadget? I logged the issue here and it is not working using the onDemand version. https://support.atlassian.com/browse/JST-83757

            Anatoli added a comment -

            Emile, it happened automatically for OnDemand customers.

            Anatoli added a comment - Emile, it happened automatically for OnDemand customers.

            Emile Weinberg added a comment -

            @Anatoli Kazatchkov Hi, will existing Confluence OnDemand customers (like me) see this issue fixed automatically or is there anything we need to do to update settings within my Confluence site? ~ thanks.

            Emile Weinberg added a comment - @Anatoli Kazatchkov Hi, will existing Confluence OnDemand customers (like me) see this issue fixed automatically or is there anything we need to do to update settings within my Confluence site? ~ thanks.

            Anatoli added a comment -

            juanpablo.salgado, the issue is fixed in version 5.1.3 of the plugin: https://marketplace.atlassian.com/plugins/confluence.extra.jira/versions

            Anatoli added a comment - juanpablo.salgado , the issue is fixed in version 5.1.3 of the plugin: https://marketplace.atlassian.com/plugins/confluence.extra.jira/versions

            Juan Pablo Salgado added a comment -

            @Anatoli Kazatchkov Do you know when the version will be release? I'm not seeing in it on the marketplace

            Juan Pablo Salgado added a comment - @Anatoli Kazatchkov Do you know when the version will be release? I'm not seeing in it on the marketplace

            Anatoli added a comment -

            I'll assume the OnDemand fix will be sometime in November 2013.

            The upgrade is currently scheduled for 11 Nov.

            Anatoli added a comment - I'll assume the OnDemand fix will be sometime in November 2013. The upgrade is currently scheduled for 11 Nov.

              tvu TruongA
              rchang Robert Chang
              Votes:
              65 Vote for this issue
              Watchers:
              83 Start watching this issue

                Created:
                Updated:
                Resolved: