Problem
Performance of requirements tree is sluggishThe project tree be behaves sluggishly.
Solution
The performance of the requirements project tree is mainly influenced by two the following factors:
- Browser used (modern browsers are dramatically faster)
- Number of issues shown in tree (only
the version of R4J
the choice of browser
the number of exposed issues
Only issues visible to the user influence the performance
...
. Issues in closed folders do not have
...
a major impact on performance.
R4J Version
Newer versions of R4J have improved tree performance. We recommend upgrading to 4.7.1 or higher.
Browser choice
For performance optimization the recommendation is to use To achieve optimal performance, use the latest version of Firefox , or Chrome.
Latest version of Microsoft Edge show is slightly less performance compared to Firefox or performant than Firefox and Chrome.Latest version of
| Warning |
|---|
Avoid Microsoft Internet Explorer |
...
, since it is no longer supported by Jira. |
Number of issues shown
The number of issues in the requirements project tree shown that are exposed to the user impacts the performance, as the browser needs to handle all the elements internally. Modern browsers can handle huge amount of elements better (see Browser section). Best practice in Our recommendation for large projects is to structure the projects by using folders. R4J – Requirements Management for JIRA use folders to group related requirements and avoid putting large numbers of issues in a single folder.
| Note |
|---|
R4J does not limit the number of issues in a single folder |
...
, but please be aware that putting thousands of requirements in a single folder |
...
will probably impact performance negatively |
...
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page Properties | ||
|---|---|---|
| ||
| Related issues when the folder is opened. |