Reindexing
Prerequisitesβ
- FieldCraft is installed in your Jira Cloud site.
- You have Jira admin access to open Configuration -> Apps -> FieldCraft: Custom Fields -> Reindex.
- You have a JQL query that targets the issues you want to recalculate.
Overviewβ
Reindexing is crucial in Jira to maintain accurate search results, optimal performance, and data integrity, especially after making changes to custom field configurations. For Jira administrators, reindexing ensures that any new configurations are consistently applied across all issues and projects.
If you're using the FieldCraft app with calculated fields, it's important for Jira administrators to reindex after updating field configurations. This not only applies the changes but also recalculates field values for older issues that haven't been accessed in a while. Reindexing ensures that calculated fields have up-to-date values, even for issues that haven't been interacted with recently.
In Jira Cloud, calculation and recalculation behavior for "Time in Status" and other calculated fields follows this model:
- Guaranteed: A user opens the issue in Issue View.
- Best-effort: The issue is updated and the app captures the update event (this may occasionally be missed due to platform limitations).
- Admin-triggered: A Jira administrator runs reindex, as described below.
For the canonical behavior and limitations, see Performance and limitations.
How to Perform a Reindexβ
To ensure your calculated fields are up to date, follow these steps to perform a reindex in Jira:
- Open Configuration -> Apps -> FieldCraft: Custom Fields -> Reindex.
- Enter the JQL to reindex only the affected issues. For example,
project = SCRUMwill target all issues within the SCRUM project. - Click Start, and make sure not to close the tab until the reindexing process completes.
