Details
-
Type:
Suggestion
-
Status: Closed (View Workflow)
-
Resolution: Fixed
-
Fix Version/s: 5.3.4
-
Component/s: Integrations - JIRA
-
Feedback Policy:
Description
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
- In JIRA, create a project with a key of TEST
- Create one issue under TEST
- On the Confluence editor, use Insert > JIRA Issue, and set the JQL to "project=TEST". Save the macro and page. One issue is shown
- Create another issue under TEST
- 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:
- Go to the page "Confluence Admin >> Cache Statistics >> Advanced"
- Search for the term "JIRA Issues".
- Change the value from "100" (default) to "1"
- 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.
Attachments
Issue Links
- duplicates
-
- Closed
-
- Closed
- has a regression in
-
CONFSERVER-37385 REGRESSION - JIRA issue macro aggressively caches, new issues take a while to appear in the issues macro
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
- Closed
-
- Closed
- relates to
-
-
- Closed
-
-
- Closed
-
JST-73783 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-