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

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

XMLWordPrintable

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

      JIRA issues macro are not refreshing automatically. They just refresh after manually refreshing or flushing the cache in Confluence. Affects JIRA Macros 5.6.11.

      Workarounds

      1. Go to Admin > Cache Statistics, and Flush All
      2. Manually refresh the macro on the page.

        1. screenshot-1.png
          screenshot-1.png
          12 kB
        2. Screen Shot 2016-08-23 at 2.42.10 PM.png
          Screen Shot 2016-08-23 at 2.42.10 PM.png
          39 kB
        3. Screen Shot 2016-08-23 at 2.42.23 PM.png
          Screen Shot 2016-08-23 at 2.42.23 PM.png
          113 kB

          Form Name

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

            ACM Awesome IT Dept added a comment -

            What is the solution for version 5.9.7?  Do we have to Flush All?

            ACM Awesome IT Dept added a comment - What is the solution for version 5.9.7?  Do we have to Flush All?

            Vitaly Vitaly added a comment - - edited

            If you are talking about JIRA Issues Macro
            There is a "cache" parameter that can be switched to off.

            The macro maintains a cache of the issues which result from the JIRA query. If the 'cache' parameter is set to 'off', the relevant part of the cache is cleared each time the macro is reloaded. (The value 'false' also works and has the same effect as 'off'.)
            Note: This parameter is available only if you insert the macro via wiki markup or by editing the storage format of the page. The macro browser does not offer this parameter.

            Works like a charm

            Vitaly Vitaly added a comment - - edited If you are talking about JIRA Issues Macro There is a "cache" parameter that can be switched to off. The macro maintains a cache of the issues which result from the JIRA query. If the 'cache' parameter is set to 'off', the relevant part of the cache is cleared each time the macro is reloaded. (The value 'false' also works and has the same effect as 'off'.) Note: This parameter is available only if you insert the macro via wiki markup or by editing the storage format of the page. The macro browser does not offer this parameter. Works like a charm

            Stefano Romano added a comment -

            Please, Also consider us in Lastminute.Com which are affected by this bug.

            We have many confluence report which contains many different filter macros: it's very "boring" to manually updates every single macro.

            Thanks for your kind cooperation.\

            SR

            Stefano Romano added a comment - Please, Also consider us in Lastminute.Com which are affected by this bug. We have many confluence report which contains many different filter macros: it's very "boring" to manually updates every single macro. Thanks for your kind cooperation.\ SR

            nattle added a comment -

            100% agree, I rely on this feature to communicate status to managers, having to constantly refresh this data defeats the point and has caused confusion multiple times.

            I'd rather have these pages load 10x as slow and have the correct data than constantly have to add a caveat that the data is live, except that it's really not live.

            nattle added a comment - 100% agree, I rely on this feature to communicate status to managers, having to constantly refresh this data defeats the point and has caused confusion multiple times. I'd rather have these pages load 10x as slow and have the correct data than constantly have to add a caveat that the data is live, except that it's really not live.

            Matt Ward added a comment -

            This issue should not take more than a year to close. Please fix this. Just comment out the caching code or something to get it working even if it is less than optimal. You can't break it much worse than it is already broken. My opinion is that outdated data is worse than no data at all.
            For a company that promotes itself as agile, I'm not seeing much agility. Please escalate.

            Matt Ward added a comment - This issue should not take more than a year to close. Please fix this. Just comment out the caching code or something to get it working even if it is less than optimal. You can't break it much worse than it is already broken. My opinion is that outdated data is worse than no data at all. For a company that promotes itself as agile, I'm not seeing much agility. Please escalate.

            Patrick PJ Haas added a comment -

            Upvoting for focus. We also use Confluence + Jira macro to deliver updates to our customer.

            Patrick PJ Haas added a comment - Upvoting for focus. We also use Confluence + Jira macro to deliver updates to our customer.

            justin smith added a comment -

            Any news on this?

            Thanks,
            Justin

            justin smith added a comment - Any news on this? Thanks, Justin

            Minh Tran added a comment -

            Dear all,

            One of our engineer starts investigating on this issue. Please wait further update on this ticket

            Best regards,
            Minh Tran
            Confluence BugMaster
            Atlassian

            Minh Tran added a comment - Dear all, One of our engineer starts investigating on this issue. Please wait further update on this ticket Best regards, Minh Tran Confluence BugMaster Atlassian

            murthy manjunath added a comment -

            Team,

            Could you please update on this request ?

            murthy manjunath added a comment - Team, Could you please update on this request ?

            Steven Adedoyin added a comment -

            Any news on this ticket?

            Steven Adedoyin added a comment - Any news on this ticket?

              qpham@atlassian.com Quan Pham
              rgadami Rodrigo Girardi Adami
              Affected customers:
              78 This affects my team
              Watchers:
              86 Start watching this issue

                Created:
                Updated:
                Resolved: