NEW:
- You can now manage requirement to Jira relationships, learn about it in our docs.
NEW:
- You can now manage requirement to Jira relationships, learn about it in our docs.
RY-1464 Fix an exception in the import/export
RY-1428 Fixed the backup tool, which set the wrong IDs for existing requirements.
RY-1406 Due to changes in Confluence 8.8, we've changed a lot our internal libraries. We're just publishing the Jira side to be consistent. It is not necessary to upgrade the Jira plugin for the sole compatibility of Confluence 8.8.
RY-1428 Fixed the backup tool, which set the wrong IDs for existing requirements.
RY-1406 Due to changes in Confluence 8.8, we've changed a lot our internal libraries. We're just publishing the Jira side to be consistent. It is not necessary to upgrade the Jira plugin for the sole compatibility of Confluence 8.8.
RY-1365 Fix the "Jira bulk issue creation" jobs (launched from Confluence), which were displayed as running forever when the thread was stopped abruptly.
RY-1365 Fix the "Jira bulk issue creation" jobs (launched from Confluence), which were displayed as running forever when the thread was stopped abruptly.
RY-1328 Updated links to Requirement Yogi in Confluence, since RY 3.6.3 had to update all URLs for compatibility with Confluence 8.6.0.
Note: The next version will require Jira 9.4 (see the compatibility matrix).
RY-1328 Updated links to Requirement Yogi in Confluence, since RY 3.6.3 had to update all URLs for compatibility with Confluence 8.6.0.
Note: The next version will require Jira 9.4 (see the compatibility matrix).
RY-1312 Compatibility with Requirement Yogi 3.6.0 in Confluence.
RY-1312 Compatibility with Requirement Yogi 3.6.0 in Confluence.
RY-1301 Add logs to help a customer diagnose an issue with setting fields with Script Runner.
RY-1301 Add logs to help a customer diagnose an issue with setting fields with Script Runner.
RY-1271 Fix exception in the Jira create dialog, when changing issue type and there are associated requirements.
RY-1271 Fix exception in the Jira create dialog, when changing issue type and there are associated requirements.
With 3.5.2, it is possible to migrate Requirement Yogi data to the cloud using JCMA. See Migrating to the Cloud.
With 3.5.2, it is possible to migrate Requirement Yogi data to the cloud using JCMA. See Migrating to the Cloud.
In this release, we integrate with Confluence and Jira cloud migration assistant.
In this release, we integrate with Confluence and Jira cloud migration assistant.
RY-1131 Fix: Baselined requirements couldn't be removed from Jira issues.
RY-1131 Fix: Baselined requirements couldn't be removed from Jira issues.
The highlight of this release is RY-1089, which allows administrators to export data and reimport it on a new Jira instance. See the documentation.
The highlight of this release is RY-1089, which allows administrators to export data and reimport it on a new Jira instance. See the documentation.
We are introducing a new technical library for our front-end, ReactJS.
Although there is no visible benefit for customers at this time, this change is necessary to keep our product interesting for the developers who work on it.
We've also worked on the queue management, to change the way threads are managed.
If you notice any issue with this release:
We are introducing a new technical library for our front-end, ReactJS.
Although there is no visible benefit for customers at this time, this change is necessary to keep our product interesting for the developers who work on it.
We've also worked on the queue management, to change the way threads are managed.
If you notice any issue with this release:
RY-1073 Advanced Roadmaps in Jira 8.13 had a conflict with Requirement Yogi.
RY-1073 Advanced Roadmaps in Jira 8.13 had a conflict with Requirement Yogi.
RY-1050 Fix error with Firefox in the Sprint boards.
RY-1050 Fix error with Firefox in the Sprint boards.
RY-1036 Some messages from the queue were rejected depending on the configuration. It meant that some issues may not be up-to-date for customers using RY 3.2.0 to 3.2.1, until they upgrade to 3.2.2.
If you upgrade from 3.1.x, please see important notices on the Release Notes for 3.2.
This is the "LTS" version, which means this is the last version for Jira 8.5. Please upgrade to Jira 8.13 or above.
RY 2.5.19 is the minimum required on the Confluence side.
RY-1036 Some messages from the queue were rejected depending on the configuration. It meant that issues may not be up-to-date for some customers using RY 3.2.0 to 3.2.1, until they upgrade to 3.2.2.
If you upgrade from 3.1.x, please see important notices on the Release Notes for 3.2.
This is the "LTS" version, which means this is the last version for Jira 8.5. Please upgrade to Jira 8.13 or above.
RY 2.5.19 is the minimum required on the Confluence side.
We're introducing the ability to choose whether requirements should be visible for anyone on an issue, or only visible for users who can access the requirements in Confluence.
Please choose now, as we will save the history and send the notifications differently depending on the situation.
More information in the Release Notes for 3.2.
This is the "LTS" version, which means this is the last version for Jira 8.5. Please upgrade to Jira 8.13 or above.
We're introducing the ability to choose whether requirements should be visible for anyone on an issue, or only visible for users who can access the requirements in Confluence.
Please choose now, as we will save the history and send the notifications differently depending on the situation.
More information in the Release Notes for 3.2.
This version requires RY 2.5.19 or above on the Confluence side.
This is the "LTS" version, which means this is the last version for Jira 8.5. Please upgrade to Jira 8.13 or above.
If you have 3.0.9, it is useful to upgrade to 3.0.10 for the first item:
If you have 3.0.9, it is useful to upgrade to 3.0.10 for the first item:
RY-920 When bulk-creating Jira issues based on Requirements from the Confluence side, it is now possible to use a variable for the assignee field.
RY-920 When bulk-creating Jira issues based on Requirements from the Confluence side, it is now possible to use a variable for the assignee field.
RY-899 Fix an exception during the execution of the upgrade task, and write more info in the logs in other unexpected situations.
RY-899 Fix an exception during the execution of the upgrade task, and write more info in the logs in other unexpected situations.
Following the major release of Requirement Yogi 3.0 on the Confluence side, this is the data model upgrade on the Jira side.
Check out the Release Notes for RY 3.0!
Following the major release of Requirement Yogi 3.0 on the Confluence side, this is the data model upgrade on the Jira side.
Check out the Release Notes for RY 3.0!
Please upgrade to RY 3.x, it is not easy to rebuild very old versions of plugins. This bugfix is only provided for temporary purposes.
Please upgrade to RY 3.x, it is not easy to rebuild very old versions of plugins. This bugfix is only provided for temporary purposes.
RY-865 The Requirement Yogi field prevented creating Jira issues as an anonymous user.
RY-865 The Requirement Yogi field prevented creating Jira issues as an anonymous user.
RY-830 When another Jira app defines a page with the same name, Jira may disable the older one. Thus, we've renamed our pages in Jira to prevent collisions.
RY-830 When another Jira app defines a page with the same name, Jira may disable the older one. Thus, we've renamed our pages in Jira to prevent collisions.
RY-798 Restore the "resync" button in the Jira dialog
RY-798 Restore the "resync" button in the Jira dialog
See Release Notes 2.6.5 for more details:
See Release Notes 2.6.5 for more details:
RY-782 Fix bug: Javascript error in the custom field, when editing it.
RY-782 Fix bug: Javascript error in the custom field, when editing it.
See our release notes:
See our release notes and screenshots of the new dialog:
See Release notes 2.6.0.
In this version, we have also upgraded many libraries, hence the major version number. Risk is slightly higher than usual, but we are available if you meet a compatibility issue.
Jira 8.5+ is required.
See Release notes 2.6.0.
In this version, we have also upgraded many libraries, hence the major version number. Risk is slightly higher than usual, but we are available if you meet a compatibility issue.
Jira 8.5+ is required.
RY-754 Better management of the timeout of the queue in Jira.
RY-754 Better management of the timeout of the queue in Jira.
RY-750 Correction of a Null Pointer Exception when adding a link, and when the Confluence version is very old.
RY-709 API to make it possible in our traceability matrix in Confluence to list custom fields faster, by only loading the necessary data
No visible change, and upgrading is only useful if you have 2.5.19+ on the Confluence side too.
RY-750 Correction of a Null Pointer Exception when adding a link, and when the Confluence version is very old.
RY-709 API to make it possible in our traceability matrix in Confluence to list custom fields faster, by only loading the necessary data
No visible change, and upgrading is only useful if you have 2.5.19+ on the Confluence side too.
Jira 7.13 is not supported anymore, please upgrade to the next "Long term support" version if you want to benefit from upgrades of Requirement Yogi.
This probably is our last release for Jira 7.13 and above, which is reaching it end of life. Please migrate to Jira 8.5+.
This probably is our last release for Jira 7.13 and above, which is reaching it end of life. Please migrate to Jira 8.5+.
RY-670 Clicking on the "Synchronize" button should synchronize the requirements immediately.
We will extend the second feature for Data Center customers after the performance is confirmed to be good on large instances with clusters.
We will extend the second feature for Data Center customers after the performance is confirmed to be good on large instances with clusters. If you are unsure, you do not necessarily need to associate this searcher with our custom field.
This release introduces a queue of events between Jira and Confluence, and thus requires you to go to the Jira administration and set a username for the connection. See Release Notes 2.5 for more details.
This release introduces a queue of events between Jira and Confluence, and thus requires you to go to the Jira administration and set a username for the connection. See Release Notes 2.5 for more details.
RY-532 The popup which showed requirements details would be duplicated if one edited the field, then tried to view the popup again.
RY-532 The popup which showed requirements details would be duplicated if one edited the field, then tried to view the popup again.
Support for RY-480, the bulk-creation of Jira issues from the search in Confluence. Support for large sets (beyond 100).
Support for RY-480, the bulk-creation of Jira issues from the search in Confluence. Support for large sets (beyond 100).
There will be another release soon with new features, we just wanted to deliver the bugfixes quickly.
There will be another release soon with new features, we just wanted to deliver the bugfixes quickly.
We can create Jira issues in bulk from requirements (see details). See also the Release notes 2.3.
RY-492 Fix the rename feature (triggered from the Confluence side), which was producing a "field not marked as ignorable" error in Jira.
RY-492 Fix the rename feature (triggered from the Confluence side), which was producing a "field not marked as ignorable" error in Jira.
This version is the first Data Center-approved!
The real changes were in 2.2.5, see the release notes.
Additionally, we've included RY-469 to ensure our upgrade tasks are executed in the background instead of delaying the installation of the plugin.
The Jira module with Data Center support remains free, only the Confluence part is paid.
Please be reminded that we follow Atlassian's Enterprise Releases, Jira 6.6 and Confluence 6.6 will be 2 years old in November. Please upgrade to
Thank you all for your bug reports and reviews (Psst... Did you give us a rating on our Marketplace page? It's pretty important for visibility, and it doesn't necessarily requires leaving a review!)
This version is the first Data Center-approved!
The real changes were in 2.2.5, see the release notes.
Additionally, we've included RY-469 to ensure our upgrade tasks are executed in the background instead of delaying the installation of the plugin.
The Jira module with Data Center support remains free, only the Confluence part is paid.
Please be reminded that we follow Atlassian's Enterprise Releases, Jira 6.6 and Confluence 6.6 will be 2 years old in November. Please upgrade to
Thank you all for your bug reports and reviews (Psst... Did you give us a rating on our Marketplace page? It's pretty important for visibility, and it doesn't necessarily requires leaving a review!)
See Release notes 2.2.5 for Jira:
See release notes for more details.
There are many changes in the Confluence module (see the release notes), but it's only bugfixes for the Jira part:
Note: We're looking for customers who need an integration with other products (ReqIF, CaliberRM, Excel, etc). If you are one of them, please contact us.
RY-68 Remember the baseline number in the "add link to requirement" dialog, so we always link to requirements of the same baseline. This preference is saved per user, per project.
RY-267 Extend the usage of the queue of messages between Requirement Yogi for Confluence and Jira, in order to accelerate the performance on both the submission of pages in Confluence and in the background tasks of Jira.
RY-243 If using both Requirement Yogi and Testing & Compliance, then mentioning a Jira issue in a test sheet will link the issue to the requirement.
Compatibility with the latest Test & Compliance features:
Added the ability to list the relationships between Jira projects and Confluence spaces in the Jira administration.
The new API has a few user-facing features:
It means more reliable and up-to-date synchronizations.
As a side note, it is possible to change the synchronization properties in the Confluence administration, be notified by email when there's a failure, and switch back and forth between the old and new version of the API in the JIRA administration.
RY-201 In the "Insert link" dialog, add a new screen named "baselines", which lets you add links from a baseline.
Fix RY-176: Requirement Yogi 1.8.2 produced a Javascript error that broke Jira. This is now fixed in 1.8.3.
RY-160 Add an issue tab panel for the history of Requirement Yogi links.
Issue links don't generally trigger notifications for watchers in Jira.
With RY-150, Requirement Yogi will notify watchers when links related to requirements have changed:
Some customers still can't see some of Requirement Yogi's admin screens: Adding more "component-import" in atlassian-plugin.xml in a new attempt to fix RY-125.
Fix Requirement Yogi's admin screens in some versions of Jira (see RY-125).
RY-80 Fix synchronization error when there are Applinks to other servers than Confluence.
Requires Java 8.
This version requires Jira 7.x.
Contains the same bugfixes as RY for Jira 7.x, but backported:
This version has a very slight bug: It sometimes fails at recognizing the keyboard shortcut Alt + Shift + R to display the Requirement Yogi Links dialog.
We display more detail about errors in Jira when the synchronization with Confluence didn't succeed.
When a requirement was moved from one space to another, update the link and the properties of the requirement in Jira. Also, post the updated title of the Jira issue.
First version of the integration for Requirement Yogi between Jira and Confluence.