Yogi Testing
Early access
We’re making this feature public to gain feedback from customers. See below how to join the usergroup.
September 2025: Initialization of the project,
October 2025: First EARLY ACCESS release,
January 2025: Expected first production release[1]
[1] Like all IT projects, dates of deliveries are not contractual.
“Requirement Yogi for Jira” is being extended with testing capabilities.
The project started on ,
We’ve formed a usergroup, and other user interviews will happen,
Early access versions have been published since ,
We aim for the project to be useful in production around January 2026, with the usual disclaimer related to IT projects and dates of deliveries,
How to give input to the Yogi Testing team
Please submit issues to our Jira: https://support.requirementyogi.com/
We have a Slack community, which you can join by asking on a Jira ticket above. Keep in mind you’re connecting with real developers, with limited bandwidth, so they will reject some requests.
What to expect
This new module will be a new tab on Jira projects. It will at least manage Test Cycles, Test Cases, Test Plans, and of course, Test Executions.
There will be an API. We don’t have plans for automations at this time.
We will tune rate limits and database sizes experimentally during the first year.
It will be part of our Jira app, so there will be:
Requirement Yogi for Confluence - Define the requirements
Requirement Yogi and Testing for Jira - Required for most customers, since it’s the existing module that allows linking requirements to Jira issues. Will contain “Yogi Testing”.
Big thanks to the community
Our ability to develop this new feature in such a short time is linked to the ability to reach out to our community, so thank you for providing this feedback.