Reduce the limit for change history items
This recommendation is shown when Jira’s issue index includes a large amount of change history, which increases index size and can slow down indexing and search performance.
Signals used
Details of how we detect this issue.
Conditions
The following conditions need to occur together:
At least one key experience, such as viewing or editing an issue, shows degraded page load times (RFU).
JQL execution time is degraded
The limit for indexing change history items (
jira.safeguards.indexing.issue.changelogs) is above 100.
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. This helps us confirm that users are actually experiencing slower page loads, not just one-off spike. |
RFU breakdown - JQL execution time | We break down RFU time into backend operations and specifically check whether the JQL execution time portion is degraded compared to its historical baseline. |
Change history limit | We check your current limit for indexing change history ( |
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 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:
periods where a high volume of change history in the index caused performance issues
whether tuning how much change history is stored in the index reduces how often this recommendation appears
Recommended actions
Adjust change history index limit
If change history is a significant contributor to index size, consider reducing how much history is indexed. Depending on your Jira version and configuration, this may involve adjusting how long change history is retained in the index or which parts of history are indexed.
The goal is to keep enough history indexed to support your most common searches and audits, while avoiding indexing every small change over the full lifetime of every issue.
For details and recommended values for change history, see Safeguards to Jira index.
Was this helpful?