...
Confluence pages:
100 requirements per page. Our software supports more, but Confluence tends to timeout while displaying them. Don’t worry! Your requirements are still here, and taken into account, but the image of the macros don’t display. We recomment splitting your requirements in multiple pages.
Traceability matrix:
The total cell count of the matrix is limited to 100 000 (For example, 10 000 rows of 10 columns),
Up to 500 requirements per page,
Up to 15 000 requirements for an export,
A time limit of 2 minutes per traceability matrix (both for export and web).
If you display too many Jira issues (more than 500) or Jira columns, it will probably take us more than 2 minutes to get the information from Jira, resulting in a timeout.
Dependencies:
Requirements to requirements links : 15 to 200 at most. We don’t have a hard limit on this topic, but the UI will perform slowly in many places, our product being based on the assumption that relationships are close relationships.
Jira Issues:
Same as dependencies, 200 at most. We do not recommend linking one issue per requirement. It implies you are managing the same data as requirements and as a Jira issue. You will then have trouble keeping them up to date with Confluence in mass.
Format
For a correct indexation, requirements cannot be placed in a column or row with a header configuration.
If you are using an horizontal table, make sure the configuration is set to ‘Header row’ only. This way we’ll be able to index the requirement and properties.
If you are using a vertical table, make sure the configuration is set to ‘Column row’ only.
Variants
We limit the number to 5 variants per space, except when generating variants from Scroll documents. You can contact us via support ticket to extend this limit, on a case by case basis. In most cases, if you need more than 5 variants, you are trying to do something that is not advisable (The variants are not intended to be used as a version control system, for instance).
...