Summary

After creating a custom field(or renaming the field) in JIRA, the JIRA Issue macro won't enable the sorting for that custom field until Confluence is restarted.

Environment

Tested with Confluence 6.2.3 and JIRA 7.3.0

Steps to Reproduce

1. In JIRA, create a Custom Field.
2. In Confluence, insert a JIRA issue macro and display the custom field that you created in the first step.
3. Save the changes.

Expected Results

Sorting will be available for that custom field

Actual Results

Sorting won't be available for it, although default fields will be sortable. After restarting Confluence, the custom field will be "sortable" like the other ones.

Notes

• Flushing the cache in Confluence won't resolve.
• Rebuilding the indexing of the content won't resolve.
• Clearing the browser's cookies won't resolve.
• Sometimes, a few hours later, the field is sortable. Probably an internal job is executed in the background(unknown job).

Update 2018

With the release of Confluence 6.8.0, restarting Confluence will not work, however, clearing the plugins cache(and flushing the cache on the Cache Management page) may resolve the problem.

Workaround

Only restarting Confluence.