Pricing (Notified on February 2nd, 2016)
Requirement Yogi was initially priced in a "One feature, meaningless price" mindset. Since then, we've added JIRA integration, syntax-based search, space-scoped requirements and we plan to add more. We feel that Requirement Yogi now transforms an intranet tool (Confluence) into a requirement capture tool. With the upcoming releases, we feel that charging 15% of the price of Confluence is consistent with this service, and yet it's still an order of magnitude fewer than the alternatives.
- Any license purchased until is perpetual, and upgrades are provided for 1 year after the purchase.
- Grandfathering means that customers who have purchased before are offered a rebate for renewals.
| 10 Users | 25 Users | 50 Users | 100 Users | 250 Users | 500 Users | 2000 Users | 10,000 Users | 10,000+ Users | |
|---|---|---|---|---|---|---|---|---|---|
| Until | $10 | $150 | $150 | $150 | $150 | $298 | $498 | $798 | $798 |
From Model: 15% of Confluence | $10 | $180 | $330 | $600 | $1200 | $1800 | $2400 | $3000 | $3600 |
Bugtracking
Bugs and improvements are tracked in JIRA: https://playsql.atlassian.net/issues/?filter=10400 (Use the icon on the right of the search bar to switch to a list).
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Excerpt | ||||
|---|---|---|---|---|
| ||||
If you want to configure the Requirement Yogi plug-in, here is the administrator’s guide. |
Tips & Tricks: Administrate Requirement Yogi
The sidebar might scare you to think there are a lot of things to administrate but don’t worry, usually there isn’t much to do. These tabs are here for your information, and for you to answer and take the correct actions if you encounter discrepancies or your users have questions.
Version history
Please see the version history on the Marketplace:
...
Compliance considerations
Some customers use Requirement Yogi for legal or compliance purposes. We don't assess whether Requirement Yogi is suitable or unsuitable for this purpose, but here is some interesting information:
The coverage features, the dependency matrix, the link with JIRA are very useful tools in achieving traceability.
Requirement Yogi creates a copy of all requirements when you create baselines, including their text. The text is frozen, it can't be updated again. Links to dependencies in the same baseline are saved.
The baseline and the saved version of the requirements may be deleted if the page of the baseline is deleted.
Confluence allows deleting a version in the page history. It means a dedicated person could delete the version of the requirements that was agreed upon and saved in the baseline, so that the text of the requirement in the baseline doesn't match the text in that version of the page.
Confluence allows add-ons to change its data, notably the page history. A malevolent add-on could in theory modify an older version of a page to make it seam like a specific requirement was written.
We depend on the core behavior of Confluence and some features are intended for Agile-oriented companies with assumed positive intentions. If you regularly work with malevolent people, you may want to ask us which defensive customizations you could deploy (Notably preventing pages and versions from being deleted, configuring Applinks in a certain way for authentication purpose, setting up version-level signatures).
📬 Subscribe to our release notes
The best way to keep updated about our new features is to click on "Watch App" on the product’s page.
📢 Subscribe to our mailing list
Tune your notifications to the information you care about:
Release notes and new features
Pricing and licensing updates
Security and vulnerability notifications
New blogs and videos
Atlassian Community Q&A
Community discussions on new features
⭐️
And while you’re at it, Atlassian really gives importance to product reviews and it would really help us if you gave us one!
Thank you!