415
Customers have installed this app in at least 415 active instances.
    by Play SQLAtlassian Verified
    Play SQL is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for app quality, reliability, and support.

    Learn more

    for Confluence Server 5.10.1 - 6.5.1 and more versions
    Versions available for Confluence Server 5.3.4 - 5.10.0
    Supported
    Play SQL supports this app.

    Get support

    Data Center
    This app is compatible with the clustering and high-availability capabilities of our products.

    Writing requirements in Confluence just became fantastically easy

    Writing requirements in Confluence just became fantastically easy

    Number your requirements

    Link to requirements

    Industry-ready solution

    Professional specifications identify requirements with keys, such as "PJT-FN-001", used in test plans and Jira issues. Insert a new requirement with Alt + Shift + R, and we suggest the right key based on your scheme.

    Keep the dynamic information and change requests in Jira. Keep the static documentation in Confluence, easily accessible for tech writers, developers, and shared with your customers.

    The properties, the dependency matrix, the coverage report, the baselines for versioning and Excel export. You'll discover features you didn't know you needed for proper requirement management. Welcome to the community!

    More details

    Please fill in our survey about Requirement Management with the Atlassian suite!

    Confluence is the best place to capture requirements. Have a look at the full description of Requirement Yogi for Confluence.

    We've watched how development teams work and created Requirement Yogi so they remain zen while delivering software.

    • Insert requirement keys using Shift + Alt + R,
    • Use a scheme like "REQ-001" - Requirement Yogi suggests the next available key, so you can ensure unique keys.
    • Quickly peek into requirements by hovering over the link!
    • With properties, search on properties and reports, define metadata around requirements that suits your needs.
    • With the dependency matrix, coverage reports and Excel export, benefit from features requested by the 200+ users community.

    Discover how the best teams around the world manage requirement keys in Confluence.

    See here for the Jira integration.

    See also: Our blogpost on How to Manage Requirements in Jira and Confluence.

    Reviews for cloud

    (11)
    Sign in to write a review
    by Lara Ramsay on 2017-06-13
    The functionality of this add-on really met our needs, and we created a requirements management solution that worked extremely well for us. However, we found a defect in the tool (not generating a unique ID, which is the main point of the tool, so it was a showstopper), that has been outstanding now for over three months. The vendor was initially responsive and published fixes for us to install. Unfortunately, none of the fixes corrected the issue. Repeated requests for an update from the vendor were met with silence. We have not heard back from him in over two months and had to make the unfortunate decision to pull this add-on from our environments. Another user has also reported seeing the issue - the vendor has stopped responding to comments, see: https://playsql.atlassian.net/browse/RY-116 The functionality this add-on provides is fantastic, when it works. However, the lack of support is not something we can risk in our production environments. Unfortunate.
    2 out of 2 found this review helpful
    Was this review helpful?YesNo
    Play SQL

    Hi Lara, Thank you for raising an alert, both about this issue and about the delay in answering support. Your alert made us take two actions:

    • We will now prioritize answering to customers before advancing the rest of our work,
    • We've made a huge team effort in the last 3 weeks to resolve difficult long-standing issues, resulting in the release of 1.7.0. Although your specific problem (RY-116) is difficult for us, I believe we've either resolved it in 1.7.0 or we've made it easier for you to collect debugging information for us. That is in addition to a dozen other bugfixes/improvements, some of them equally difficult to solve (such as RY-122 - Renaming requirements).

    Once again, I'm sorry that it caused difficulties and uncertainty for you, I believe we've taken the right steps to avoid reproducing this situation.

    by Eric FOUCHER on 2016-05-26
    Just AWESOME : all those fonctionalities added with 1.4 are perfect to create requirements, index, labels, lists, ... We use it almost every day and couldn't do without it anymore ! Keep going with that kind of great ideas.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Sigrid Schoepel on 2015-06-25
    It seems helpful but I cannot find the directions in the documentation for inserting a link to the requirement.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    Play SQL

    A _link_ to a requirement: Right click on a requirement and choose "Copy link". The link will automatically be transformed into a macro when you paste it.

    by Mike Rathwell on 2015-01-27
    The more I use this plugin, the more I like it. Unlike many "requirements management systems", this plugin allows me to operate the way *I* want to operate and does what it needs to; tag and track requirements. Its functionality is deceptively simple but also deceptively powerful. I am free, largely, to form requirements documents based on the project, requirement document type, etc and this just runs along keeping track. When one adds in its intelligence in prompting for "what do you want to do" and the ability to create a requirement without ever touching the mouse, writing requirements documents is no longer painful. Just the right level of functionality for how we operate. As the product inevitably gets more features, as long as it stays as flexible and adaptable as it is today, it can only get cooler. When one adds in the stellar responsiveness of the vendor (had one thing I didn't grok early on) and we've got a winner here.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Sorin Sbarnea (Citrix) on 2014-11-10
    I am looking forward to see this plugin more mature, I have the impression that it may become really useful.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo

    Reviews for server

    (11)
    Sign in to write a review
    by Rebekkah Brown on 2017-10-19
    **updated review** I'm upping my two star review to four, and here's why: (a) The lack of support we initially complained of has more than been made of for in Play SQL's attentiveness since the original review was made. (b) I was mistaken about a change in the report macro's functionality - it's working fine! (c) Although I still wish in my heart of hearts that the custom linkage was available in bulk upload, Play SQL has explained that the tool was not intended for such massive associations, and I don't want to dock it for not meeting standards other than those it was built to meet. The tool works well to fulfill its intended purpose. (d) Also, although it would be convenient if a change made in Confluence automatically synced the requirement reference in a Jira ticket always, RY does have a way of setting up timed syncs. **initial review** I am of two minds regarding this tool. We were very excited about it initially, but have since realized it doesn't fully meet the needs of our company, based on the way we use Confluence and Jira. Even so, we were hopeful that we might be able to work with Play SQL over RY's improvement, but although we've reached out several times, we've gotten no response. This has been super disappointing as we believe this plugin could be extremely useful for us with a few additions and enhancements. If there was a way to work with Play SQL to improve the product, I'd likely be singing its praises. As it stands, we're currently looking into replacement tools that offer all the functionality we need. Some specifics: On the one hand, RY's been a helpful means of further linking specific portions of a Confluence page to Jira, and has given our developers an easier method of reviewing expectations from within their ticket where we've used the custom link. On the other hand, without being able to create the custom requirements link via Jira's bulk import, and without the update to a requirement syncing immediately with the ticket (instead of requiring manual update/sync from the ticket), much of what we originally were excited by in this add-on cannot be used. We have too many tickets for the manually adding links to each individually to be a worthwhile use of time. Also, I was particularly excited about the report macro's ability to categorize and collect requirements across pages into a single table until a recent change removed the ability to customize which columns were displayed. We were using this feature to collect one or more column's content into tables, but now have only the options "properties" and "description", which gathers much more content than we'd like. For our purposes, this feature would be much improved if we could define (as we used be able to), the key names of columns to show (i.e. gather all items with "Category" column value "ERR", and display content from columns "Requirement Title", "Details", and "ErrorMessage").
    Was this review helpful?YesNo
    Play SQL

    It is correct that Rebekkah sent two emails, the last one in January 2017. I've made a reference to the problem and its answer in the response to Lara Ramsay (below): I've recognized the issue and taken actions to solve it, namely hiring and prioritizing immediate support before long-term tasks, in order to unblock customers. I have missed passed emails and I'm sorry for that.

    Concerning your specific problem about bulk-import, let's make it clear (including for future customers) that Requirement Yogi is not designed to create one JIRA issue per requirement. JIRA Sprints should be planned independently from detailed items. It will never be practical to reference 25 requirements in 1 JIRA issue, and expect the full Confluence page to show up in the JIRA record. In such situations, it is much more useful to reference the Confluence page itself, and let the user browse to Confluence. If there is a 1-to-1 match between requirements and JIRA issues, it is better to just create JIRA issues straight away. The JIRA integration is rather designed to raise bugs referencing single requirements, that's where it becomes really useful.

    I'm not aware of the recent change you report about removing the ability to customize which columns are displayed. I rather think it's a bug, and if anyone meets it please report it to me. I've fixed urgent bugs in the past sometimes as fast as 1 day and most often in 10 days depending on the complexity, the urgency and the possibility of grouping bugfixes into a release, I'm more than happy to do it again. Check out my "versions" page to see the dates.

    When there is a customer-product fit, the benefits are huge (Features like the search, the inline editing, the reports, the baselines, the JIRA links, the Excel export and now the integration with RY Testing...). Most support requests come from customers who try to fit an existing process with this product and can't be satisfied. I usually try to accomodate such usecases, but sometimes the answer is simply to keep using their older tools, since they are customized for their needs, even if they don't involve Confluence.

    Please email me again if you are still a customer, or accept my most sincere apologies for the lack of help you've met when I missed your 2 emails.

    by Lara Ramsay on 2017-06-13
    The functionality of this add-on really met our needs, and we created a requirements management solution that worked extremely well for us. However, we found a defect in the tool (not generating a unique ID, which is the main point of the tool, so it was a showstopper), that has been outstanding now for over three months. The vendor was initially responsive and published fixes for us to install. Unfortunately, none of the fixes corrected the issue. Repeated requests for an update from the vendor were met with silence. We have not heard back from him in over two months and had to make the unfortunate decision to pull this add-on from our environments. Another user has also reported seeing the issue - the vendor has stopped responding to comments, see: https://playsql.atlassian.net/browse/RY-116 The functionality this add-on provides is fantastic, when it works. However, the lack of support is not something we can risk in our production environments. Unfortunate.
    2 out of 2 found this review helpful
    Was this review helpful?YesNo
    Play SQL

    Hi Lara, Thank you for raising an alert, both about this issue and about the delay in answering support. Your alert made us take two actions:

    • We will now prioritize answering to customers before advancing the rest of our work,
    • We've made a huge team effort in the last 3 weeks to resolve difficult long-standing issues, resulting in the release of 1.7.0. Although your specific problem (RY-116) is difficult for us, I believe we've either resolved it in 1.7.0 or we've made it easier for you to collect debugging information for us. That is in addition to a dozen other bugfixes/improvements, some of them equally difficult to solve (such as RY-122 - Renaming requirements).

    Once again, I'm sorry that it caused difficulties and uncertainty for you, I believe we've taken the right steps to avoid reproducing this situation.

    by Eric FOUCHER on 2016-05-26
    Just AWESOME : all those fonctionalities added with 1.4 are perfect to create requirements, index, labels, lists, ... We use it almost every day and couldn't do without it anymore ! Keep going with that kind of great ideas.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Sigrid Schoepel on 2015-06-25
    It seems helpful but I cannot find the directions in the documentation for inserting a link to the requirement.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    Play SQL

    A _link_ to a requirement: Right click on a requirement and choose "Copy link". The link will automatically be transformed into a macro when you paste it.

    by Mike Rathwell on 2015-01-27
    The more I use this plugin, the more I like it. Unlike many "requirements management systems", this plugin allows me to operate the way *I* want to operate and does what it needs to; tag and track requirements. Its functionality is deceptively simple but also deceptively powerful. I am free, largely, to form requirements documents based on the project, requirement document type, etc and this just runs along keeping track. When one adds in its intelligence in prompting for "what do you want to do" and the ability to create a requirement without ever touching the mouse, writing requirements documents is no longer painful. Just the right level of functionality for how we operate. As the product inevitably gets more features, as long as it stays as flexible and adaptable as it is today, it can only get cooler. When one adds in the stellar responsiveness of the vendor (had one thing I didn't grok early on) and we've got a winner here.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo

    Pricing

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing?

    Apps are billed based on the number of users in your host product. The app tier should match the licensed user tier of the Atlassian host product. For example, if you have a Confluence Server license for 25 users, you should purchase the 25-user tier for apps. Even if fewer users want to use the app than your host product license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian host product, and you're all set.

    How can I buy apps for my legacy Jira Server or Confluence Server license?

    If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:

    • Purchase the app at the non-legacy Unlimited (10000+ users) tier.
    • Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.

    Learn more

    Play SQL is an Atlassian Verified vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.

    Vendor support resources

    Documentation

    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Versions

    Version 1.9.2 Confluence Server 5.10.1 - 6.5.1 Released 2017-10-20

    Summary

    Maintenance Release

    Details

    The administration page has changed, we've distributed the options into separate tabs to make it clearer, and added the "onboarding checklist".

    • RY-200 Solve a small exception when ordering the RY Report macro,
    • RY-199 Add an onboarding checklist,
    • RY-191 Toggle the macro between "link" and "definition" of requirement.

    Installation

    1. Log into your Confluence instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Requirements Yogi via search. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Requirements Yogi. You're prompted to log into MyAtlassian. Requirements Yogi begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Confluence instance.

    To find older Requirements Yogi versions compatible with your instance, you can look through our version history page.

    Similar apps