Health check: Missing OpenSearch Mappings in Jira Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
In OpenSearch, mappings define how documents and their fields are stored and indexed. Each field in Jira, like a system field or custom field, needs to be mapped as index fields to enable search functionality. Jira creates these mappings when it starts, or when you create or update a custom field. If a mapping fails to be created, the affected field won’t be indexed, which disrupts its search functionality.
This health check verifies that all fields in your Jira instance are included in the OpenSearch index mappings.
Solution
Understand the Health Check results
Icon | Result | What this means |
✅ | The OpenSearch index has all required mappings. | No issues have been detected. |
❗ |
| Some fields are missing in the OpenSearch index mappings. Those fields aren’t currently indexed and therefore aren’t searchable. |
⚠️ | Unable to check the OpenSearch index mappings. | There was a problem checking the OpenSearch index mappings. |
Troubleshooting
Problem | Suggestion |
Some fields are missing in the mappings | You can find the reason these fields failed to create index mappings in the Jira application logs. To retry creating the mappings, restart one of your Jira nodes or update the specific custom field that is affected. Some possible reasons for the failure include: OpenSearch wasn't available at the time. Jira doesn’t have permission to create mappings on your OpenSearch index. The After you identify and resolve the problem, the affected fields might have missing data in the index. We recommend rebuilding your index to ensure its integrity. For more information, see Re-indexing Jira. |
Was this helpful?