Details
-
Suggestion
-
Status: Gathering Interest
-
Resolution: Unresolved
-
Xray DC V7.4.1
-
None
-
None
Description
In June 2022, Atlassian introduced guardrails for Jira and Confluence, aiming to reduce the impact that the data growth can have on the performance and reliability of a given instance.
The guardrails for Jira Software include several different areas and entities within the software, but this Suggestion focuses specifically on the topic of "Change history".
Change history
| Content type | Number of changeitems or changegroups associated with an issue |
|---|---|
| Guardrail | 20,000 changeitems or changegroups |
| How to find this number | Retrieve issue change history |
| Risks | We've observed these problems when operating above this guardrail: * Out of memory errors when viewing the History tab.
|
| Mitigation options |
|
As of now, Xray has many operations that add entries to the issue history, most notably when importing issues via REST API, and those entries can easily surpass the 20,000 mark recommended by Atlassian, and cause performance issues in the long run.
As a system, Xray should offer the possibility to configure, both Globally and on a project level, what actions should be excluded from logging into issue history.
Attachments
Issue Links
- relates to
-
XRAY-9789 Same imports should not create additional entries in Issue History
-
- Open
-