Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Open transparency!

Please also discover the upsides of Requirement Yogi. We are one of the rare vendors who communicate openly about the limitations, because we believe it helps managing expectations. Nevertheless, we are also better than the competitors on all the upsides (wink) so please make an accurate assessment of the product before looking at those limitations.

It is important for admins to know what are the limits of the app in terms of performance. This is what we recommend when using Requirement Yogi:

Confluence pages:

  • We noticed a decrease in performance after 100 requirement macros per page. We advise splitting your requirements in multiple pages.

  • We also advise limiting the number of links per requirement to 200.

Traceability matrix

  • We have a display limit of 500 requirements per page

  • We limit the number of requirements to 15 000 for an export

  • We also limit the number of Jira links to 1000 per matrix.

  • The total cell count of the matrix is limited to 100 000.

  • The traceability matrix will also stop collecting children after 2min of computing time.

Variants per space

We limit the number of variants per space to 5, 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).

  • No labels