Migrate the Jira index to Open Search
This recommendation is shown when we've detected that JQL query performance is degrading and your Jira instance may benefit from migrating the issue index to OpenSearch. OpenSearch allows the issue index to scale independently, which can improve search and query performance for large or growing instances.
Signals used
Details of how we detect this issue.
Conditions
The following conditions need to occur together:
The instance is not already using OpenSearch as the search platform.
JQL query execution time is degraded — either execution times are elevated compared to their historical baseline, or the number of JQL slow query events is increasing.
The issue count has been growing over the last month, showing continued data growth.
Optionally, we also consider whether continued growth at the current rate will breach guardrails within the next month.
When these conditions are met together, we surface this recommendation.
How we detect it
Signal | Details |
|---|---|
RFU degradation | We look for Ready for User (RFU) degradation - cases where key Jira experiences take significantly longer than their historical baseline. |
OpenSearch status | We check whether the instance is already using OpenSearch as the search platform. |
JQL execution time degradation | We look for cases where JQL query execution times are significantly elevated compared to their historical baseline. |
JQL slow query events | We monitor whether the number of JQL slow query events has increased. A rise in slow queries indicates that more queries are exceeding acceptable execution time thresholds. |
RFU breakdown — JQL execution time | We break down RFU time into backend operations and specifically check whether the JQL execution time portion is degraded. This tells us that time is being spent executing JQL queries during page loads, rather than in other parts of the request. |
Issue count trend | We track whether the total issue count has been growing over time. A steadily increasing issue count contributes to a larger index and can worsen query performance. |
Issue reindexing performance | We optionally monitor whether issue reindexing metrics have been increasing, which can indicate that the local index is struggling to keep up with the volume of changes. |
Filters
When this issue occurs multiple times, we group occurrences under different time filters, for example a 24‑hour or 7‑day period. In this case:
For degraded experiences, we show the highest RFU degradation from all occurrences in the selected time filter.
Frequency chart
The frequency chart shows how often this issue has occurred over time. This can help you identify patterns such as:
Specific days or times when JQL query performance gets worse.
Periods after data growth milestones (for example, large imports or increased usage) when search performance starts to degrade.
Recommended actions
Migrate to OpenSearch (requires Jira 11, or later)
Consider migrating your Jira issue index to OpenSearch. OpenSearch allows the issue index to be hosted in a dedicated, independently scalable cluster, which can significantly improve search and query performance for large instances.
For more information, see OpenSearch for Jira Data Center.
Was this helpful?