Review recent configuration changes
This recommendation is shown when Jira performance has degraded and we’ve detected recent configuration changes, such as Jira properties, database connection settings, dark features, or Marketplace apps that were installed, updated, or uninstalled.
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 issues, shows degraded page load times (RFU).
During the same time window, we’ve detected any of the following configuration changes:
Jira configuration changes
Marketplace app changes
Dark feature changes
Database configuration changes
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. |
Jira configuration changes | We look for changes to Jira application properties and system properties within the same time window. We compare the property values at the start and end of the window to detect additions, removals, or modifications. |
Marketplace app changes | We detect Marketplace apps that were installed, updated, or uninstalled in the same time window. These changes can introduce new performance regressions. |
Dark feature changes | We compare feature flags between the start and end of the time window to detect flags that were enabled, disabled, or added. |
Database configuration changes | We detect changes to the database configuration, such as connection pool sizes or wait times, by comparing database settings between Jira startup events. |
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.
For identified changes, we sum changes from all occurrences in the selected time filter.
This helps you see which configuration changes are most closely aligned with periods of degraded performance.
Frequency chart
The frequency chart shows how often this issue has occurred over time. This can help you identify patterns such as:
whether performance degradations often follow configuration changes
clusters of changes (for example, multiple app updates or property changes rolled out at once) that line up with repeated recommendations
Recommended actions
The actions shown in the recommendation are conditional. You’ll only see the changes that you’ve made.
Review and revert risky Jira configuration changes
Download the CSV file with the list of changes and review them. Look for configuration changes that affect indexing, search, caching, or other performance-sensitive settings. If you suspect a specific change contributed to the regression, consider reverting it to the previous value, especially if it is not a documented or supported setting.
Review Marketplace app changes
Download the CSV file with the list of changes and review them. Focus on newly installed apps or apps that were updated just before the degradation started. If you suspect an app is contributing to the regressions, temporarily disable or revert it to the previous version.
Review dark feature and feature flag changes
Download the CSV file with the list of changes and review them. If you enabled specific dark features, consider disabling them to check if performance returns to normal.
Review database configuration changes
Database connection settings can have a large impact on Jira performance if misconfigured. Compare your current settings with Atlassian’s recommended database configuration for your Jira version and database. If a recent change diverges from those recommendations, consider reverting it.
Was this helpful?