[JSWSERVER-21941] Indexing will break in the version bundled version if the Team field was ever deleted

Type: Bug
Resolution: Unresolved
Priority: Low (View bug fix roadmap)
Fix Version/s: None
Affects Version/s: 8.17.1
Component/s: (Advanced Roadmaps) Plan - Teams
Labels:
- ril

Introduced in Version:
8.17
Support reference count:
1
Symptom Severity:
Severity 2 - Major
Bug Fix Policy:
View Atlassian Server bug fix policy

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

Internal ticket

relates to: JPO-17527 Failed to load

Marc Dacanay made changes - 16/Oct/2024 4:06 AM

Labels

New: ril

Marc Dacanay made changes - 16/Oct/2024 4:06 AM

Remote Link

New: This issue links to "Internal ticket (Web Link)" [ 956619 ]

Bugfix Automation Bot made changes - 04/Sep/2023 12:30 PM

Introduced in Version

New: 8.17

Stasiu made changes - 04/Sep/2023 11:54 AM

Component/s	Original: Plan [ 48691 ]
Component/s		New: Plan (Advanced Roadmaps) - Teams [ 63500 ]
Key	Original: JPOSERVER-3030	New: JSWSERVER-21941
Affects Version/s	Original: 8.17.1 [ 95491 ]
Affects Version/s		New: 8.17.1 [ 95400 ]
Project	Original: Advanced Roadmaps [ 16510 ]	New: Jira Software Server and Data Center [ 12200 ]

Bugfix Automation Bot made changes - 19/Jul/2021 6:30 AM

Support reference count

New: 1

Krina made changes - 13/Jul/2021 5:43 AM

Description

Original: h3. Issue Summary

Indexing will break in the version bundled version if the Team field was ever deleted
h3. Steps to Reproduce
# Install Jira version 8.18.0
# Unlock Team custom field and restart Jira Using [this kb|https://confluence.atlassian.com/jirakb/unlock-a-locked-jira-software-custom-field-779158866.html]
# Delete Team custom field.
# Perform any action that triggers indexing. such as Creating/Editing/Transitioning issue that has value for Team custom field Or perform Full reindexing

h3. Expected Results

Action is successful. Issue index is updated
h3. Actual Results

Action proceeds but the issue index is not updated.
The below exception is thrown in the atlassian-jira.log file:
{noformat}
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)
{noformat}
h3. Workaround

We do not have a workaround at the moment. It will be added once it becomes available

New: h3. Issue Summary

Indexing will break in the version bundled version if the Team field was ever deleted
h3. Steps to Reproduce
# Install Jira version prior to 8.15.0.
# Unlock Team custom field and restart Jira Using [this kb|https://confluence.atlassian.com/jirakb/unlock-a-locked-jira-software-custom-field-779158866.html]
# 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.

h3. Expected Results

Action is successful. Issue index is updated
h3. Actual Results

Action proceeds but the issue index is not updated.
The below exception is thrown in the atlassian-jira.log file:
{noformat}
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)
{noformat}
h3. Workaround

We do not have a workaround at the moment. It will be added once it becomes available

Krina made changes - 13/Jul/2021 5:30 AM

Description

Original: h3. Issue Summary
Indexing will break in the version bundled version if the Team field was ever deleted

h3. Steps to Reproduce
# Install Jira version 8.18.0
# Delete Team custom field.
# Perform any action that triggers indexing.
# such as: Creating/Editing/Transitioning issue that has value for Team custom field

h3. Expected Results
Action is successful. Issue index is updated

h3. Actual Results
Action proceeds but the issue index is not updated.
The below exception is thrown in the atlassian-jira.log file:
{noformat}
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)
{noformat}

h3. Workaround
We do not have a workaround at the moment. It will be added once it becomes available

New: h3. Issue Summary

Indexing will break in the version bundled version if the Team field was ever deleted
h3. Steps to Reproduce
# Install Jira version 8.18.0
# Unlock Team custom field and restart Jira Using [this kb|https://confluence.atlassian.com/jirakb/unlock-a-locked-jira-software-custom-field-779158866.html]
# Delete Team custom field.
# Perform any action that triggers indexing. such as Creating/Editing/Transitioning issue that has value for Team custom field Or perform Full reindexing

h3. Expected Results

Action is successful. Issue index is updated
h3. Actual Results

Action proceeds but the issue index is not updated.
The below exception is thrown in the atlassian-jira.log file:
{noformat}
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)
{noformat}
h3. Workaround

We do not have a workaround at the moment. It will be added once it becomes available

Sachithra Dangalla made changes - 11/Jul/2021 11:58 PM

Status

Original: Needs Triage [ 10030 ]

New: Gathering Impact [ 12072 ]

Sachithra Dangalla made changes - 11/Jul/2021 11:58 PM

Remote Link

New: This issue links to "JPO-17527 (JDOG)" [ 564713 ]

Krina created issue - 09/Jul/2021 2:15 PM

Assignee:: Unassigned

Reporter:: Krina

Affected customers:: 0 This affects my team

Watchers:: 2 Start watching this issue

Created:: 09/Jul/2021 2:15 PM

Updated:: 16/Oct/2024 4:06 AM

Jira Software Data Center

Details

Description

Issue Summary

Steps to Reproduce

Expected Results

Actual Results

Workaround

Attachments

Issue Links

Forms

Activity

People

Dates

Backbone Issue Sync