Details
-
Suggestion
-
Resolution: Timed out
-
None
-
None
Description
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
The JIRA issues macro caches JIRA searches on a per-user basis (i.e. each user's jira issues are cached separately). I think this has limited value for improving performance at a potentially high cost of storing the information. Also, many users don't realize their issues are being cached. A common question is "Why aren't my issues being updated? I've changed something but jiraissues macro isn't showing it."
Attachments
Issue Links
- relates to
-
CONFCLOUD-22845 Remove caching from JIRA issues macro
- Closed