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

« Previous Version 3 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.

Performance

Some limitations are due to us; Others are made necessary due to the Confluence API.

  • 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.

    • 15 links per requirement, and 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.

  • 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,

    • Up to 1000 Jira issues per page,

    • A time limit of 2 minutes per traceability matrix (both for export and web).

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).

Features we don’t have on the Cloud

  • There is no popup on the Cloud when hovering over requirements. It’s impossible to do it, because Confluence Cloud doesn’t have an API for that. It was replaced by the intermediate screen with all of the details of the requirement.

  • No inline transformations. It was replaced with the Page transformations Transformation Wizard, which is, frankly, awesome 😉.

  • No labels