Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.4.0, 7.6.0
-
12
-
Severity 3 - Minor
-
1
-
Description
Issue Summary
The custom fields information is cached in JIM without being actively invalidated so that newly created Jira custom fields is missing in the cache resulting in Jira issue macro column is not sortable.
The fix might be
- find a event to invalidate the cache
- save ids in JIM to bypass the custom field ids checking.
Steps to Reproduce
- Add a new custom field in Jira
- Edit a ticket to include this fields with a value
- Update Jira issues macro in Confluence to display this issue with the new column
Expected Results
This column should be sortable
Actual Results
Sorting triangle button is missing for the new column.
Workaround
Wait for cache expires
or restart Confluence
or re-enable Jira issue macro plugins
Manually invalidate "Jira Issues Macro Fields" in admin panel "Cache Management"
Attachments
Issue Links
- depends on
-
CONFSERVER-54180 Jira Issue Macro error messages do not match Jira error messages
- Long Term Backlog
- duplicates
-
CONFSERVER-46299 Some column in JIRA Issue Macro is not able to sort
- Closed
-
CONFSERVER-52934 Custom Field(new or renamed field) in JIRA Issue Macro is not "sortable" until Confluence is restarted.
- Closed
-
CONFSERVER-57838 Jira Issues Macro in Confluence sometimes loses sorting ability on some columns
- Closed