-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
8.17.1
-
8.17
-
1
-
Severity 2 - Major
-
Issue Summary
Indexing will break in the version bundled version if the Team field was ever deleted
Steps to Reproduce
- Install Jira version prior to 8.15.0.
- Unlock Team custom field and restart Jira Using this kb
- Delete Team custom field.
- Perform any action that triggers indexing. such as Creating/Editing/Transitioning issue that has value for Team custom field Or performs Full reindexing
- Indexing will not be successful an you will receive the below error
- Upgrade to 8.17.1 and the error continues.
Expected Results
Action is successful. Issue index is updated
Actual Results
Action proceeds but the issue index is not updated.
The below exception is thrown in the atlassian-jira.log file:
2021-07-02 10:57:37,238+0000 IssueIndexer:thread-2 INFO recovery_admin 539x153473x1 y2z34u 92.109.7.32 /secure/admin/IndexReIndex!reindex.jspa [c.a.j.w.a.admin.index.IndexAdminImpl] Re-indexing is 18% complete. Current index: Issue 2021-07-02 10:57:57,262+0000 IssueIndexer:thread-7 WARN recovery_admin 539x153473x1 y2z34u 92.109.7.32 /secure/admin/IndexReIndex!reindex.jspa [c.a.jira.index.AccumulatingResultBuilder] java.lang.IllegalStateException: Team custom field ID cannot be found java.lang.RuntimeException: java.lang.IllegalStateException: Team custom field ID cannot be found at com.atlassian.jira.index.DefaultIndex$Failure.<init>(DefaultIndex.java:100)
Workaround
We do not have a workaround at the moment. It will be added once it becomes available
- links to
- relates to
-
JPO-17527 Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|