Requirement Yogi - Requirements Management for Confluence

We are currently evaluating RY in Confluence and JIRA. So far, I am convinced that RY will be the right tool for us, except that the cloud version cannot set baselines, yet. I consider this an essential feature in requirements management. I upvote for implementing baselines in the cloud version of RY. Another feature that is missing (even though not this crucial) is that we cannot see the Xray test sets/cases/runs in the traceability matrix. I upvote for implementing this as well. Otherwise, as said, RY seems to be the tool of choice.

• 

  Requirement Yogi

  Hey Andreas,

  Thank you so much for your review and feedback on the cloud version.

  Concerning Baselines, we have introduced variants in October 2022, allowing you to have multiple versions of a requirement. You can find a quick tutorial in the documentation : https://docs.requirementyogi.com/cloud/variants.

  And about the Xray fields in the traceability matrix, thank you for raising that issue to us, we’ve added that feature to the backlog.

  Have a great day ! 😊

  Best regards,

  Mileva

Hi Team, I tried the free install for my cloud version but I couldn't get the baseline feature. can someone guide me on how to make use of baseline from this app. Thanks, Rahini

• 

  Requirement Yogi

  Hi Rahini,

  Thank you for your review! The cloud version doesn’t have the baselines yet, it is written in the roadmap screen. If you have further questions, feel free to use the “Support” tab instead of the “Reviews”, we are very active.

  I’ll count your review as an upvote for the baselines!

  Best regards,

  Adrien Ragot

My company needed a requirements tracking and managment tool for traceability. We have been using requirements yogi for about 2 years and I am very happy with the features. Requirements Yogi is packed with feature's and I cannot wait until the cloud version is complete. Pros: 1. Requirements Creation in tables. 2. Unique Requiremnt Keys. 3. Ability to Link Requirements in multiple pages, Inbound and Outbound. 4. Ability to Show Requirements. 5. Ability to link requirements in Jira Tickets. 6. Ability to create a traceability matrix. 7. Ability to export a traceability matrix. Cons: 1. Speed, this is not requirements yogi's fault. The usage of the cloud comes at the cost of speed.

Requirement Yogi is a nice combination of lightweight, flexible, and powerful. I appreciate that the requirement definitions are tied to the Confluence tables, so you don't have to create them in another interface that might be harder for users to track down. The traceability matrices are also very handy and easy to use, both in the RY interface and embedded in Confluence pages. The team has been very responsive in resolving bugs as well.

• 

  Requirement Yogi

  Hey Jackie,

  Thank you a lot for this review. The whole team is glad that our product fits your needs and you like it!

  We always try to do our best at the support and I am glad you noticed it! Feel free to come back to us at any time.

  Thanks again,

  Best regards,

  Jérôme R.

We use Requirements Yogi for maintaining requirement information for a number of traditional and also few quite unusual use cases and overall we are very happy with it and the vendor. We started a few years ago in Data Center and have within the last year migrated to Cloud. The early versions of the Cloud implementation lacked some important features for us (Baselines, RY Link macro behavior, aspects of the reporting functions). But what has been refreshing for a jaded old technologist like me is just how responsive the RY team have been in listening to our needs, being very transparent with the challenges (there many restrictions from Atlassian for Cloud add-on vendors) and ultimately delivering solutions through constant enhancements (and occasional bug fixes). In some cases developing new features just support our unique use case. Very rare these days. Over this time the Cloud version has become a very powerful and flexible tool, now with some features exceeding DC capabilities (I think, haven't check back lately). I will say optimal usage requires a decent time investment, in reading all the docs, watching all the videos and then most importantly, prototyping your end to end use cases. There is some room for improvement in their docs and training materials, they are better than average, but do not get deeply into some topics, nor provide enough "best practices" for areas where there are multiple implementation options. Thus the need to prototype for your needs extensively.

• 

  Requirement Yogi

  The whole team loves you, Drew <3

  Thank you for your nice and complete review, it will be useful for other customers when choosing our product, and it's important to have key people like you to help us polish the features and nail the usecases for everyone!