Minor version update

• RY-1260 Provide more info when a Jira user can't see Confluence requirements.

• RY-1260 Provide more info when a Jira user can't see Confluence 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.

See the release notes.

In this release, we integrate with Confluence and Jira cloud migration assistant.

See the release notes.

• RY-1146 APIv12: Make it possible to rename requirements using queue messages, and save the audit trail when doing so.
• RY-1194 Compatibility with Jira 9.6.

• RY-1146 APIv12: Make it possible to rename requirements using queue messages, and save the audit trail when doing so.
• RY-1194 Compatibility with Jira 9.6.

• RY-1146 APIv12: Make it possible to rename requirements using queue messages, and save the audit trail when doing so.

RY-1131 Fix: Baselined requirements couldn't be removed from Jira issues.

RY-1131 Fix: Baselined requirements couldn't be removed from Jira issues.

• RY-1124 Make it possible to process queue messages of other applinks, when one has failed,
• RY-1123 Trigger the queue when an issue is deleted, renamed or moved.

• RY-1124 Make it possible to process queue messages of other applinks, when one has failed,
• RY-1123 Trigger the queue when an issue is deleted, renamed or moved.

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.

• RY-1089 Import/export in CSV,
• RY-1109 Fix the "baseline upgrade/downgrade" button in Jira.

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.

• RY-1089 Import/export in CSV,
• RY-1109 Fix the "baseline upgrade/downgrade" button in Jira.

• RY-1099 Ability to connect Jira and Confluence, even if there are separate administrators for each application,
• RY-1096 Improve the XML export of the custom field, so that it displays nicely in Confluence's Jira report,
• RY-1100 The "queue" screen in the administration didn't display in Jira 9.x.

• RY-1099 Ability to connect Jira and Confluence, even if there are separate administrators for each application,
• RY-1096 Improve the XML export of the custom field, so that it displays nicely in Confluence's Jira report,
• RY-1100 The "queue" screen in the administration didn't display in Jira 9.x.

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:

• Please use the "Capture logs" feature in the administration of Requirement Yogi,
• You can safely downgrade to a version 3.3.x,
• Contact us via a Jira ticket.

Release notes for version 3.4.0

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:

• Please use the "Capture logs" feature in the administration of Requirement Yogi,
• You can safely downgrade to a version 3.3.x,
• Contact us via a Jira ticket.

Release notes for version 3.4.0

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-1025 Upgrade the Javascript in preparation for Jira 9.0 (still EAP), and drop the support for Internet Explorer,
• RY-1026 Change the logos,
• RY-1046 Synchronization: Split the "reset" and "create" operations,
• RY-1048 Fix a vulnerability by upgrading a library (GSON).

• RY-1025 Upgrade the Javascript in preparation for Jira 9.0 (still EAP), and drop the support for Internet Explorer,
• RY-1026 Change the logos,
• RY-1046 Synchronization: Split the "reset" and "create" operations,
• RY-1048 Fix a vulnerability by upgrading a library (GSON).

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:

• RY-975 Since 3.0.9, there was a red error message on Jira issues which had our custom field, introduced by RY-695.
• RY-973 Change in behavior: The creation of Jira issues in bulk is now limited to 5 minutes.
• RY-959 Tune the caches: Add a maximum cache size, remove unnecessary cache, make another cache local.
• RY-957 On the function requirementYogiKeys(), the results were erroneous if a requirement had been deleted, because boolean values FALSE and NULL were considered differently in SQL.

If you have 3.0.9, it is useful to upgrade to 3.0.10 for the first item:

• RY-975 Since 3.0.9, there was a red error message on Jira issues which had our custom field, introduced by RY-695.
• RY-973 Change in behavior: The creation of Jira issues in bulk is now limited to 5 minutes.
• RY-959 Tune the caches: Add a maximum cache size, remove unnecessary cache, make another cache local.
• RY-957 On the function requirementYogiKeys(), the results were erroneous if a requirement had been deleted, because boolean values FALSE and NULL were considered differently in SQL.

• RY-695 For new customers, initialize with 2 default relationships instead of 4, because it seems to be a recurrent source of confusion.
• RY-946 Fix the "Add all" button to save the excerpts of the requirements.
• RY-954 Since the company has changed named (Play SQL -> Requirement Yogi), rename the references inside the product.
• RY-938 Upgrade a library (Jsoup, to 1.14.3),
• RY-955 Tell the administrator if upgrade tasks aren't done. Also display the "applink ID" in a few places together with the application name, for ease of administration.

• RY-695 For new customers, initialize with 2 default relationships instead of 4, because it seems to be a recurrent source of confusion.
• RY-946 Fix the "Add all" button to save the excerpts of the requirements.
• RY-954 Since the company has changed named (Play SQL -> Requirement Yogi), rename the references inside the product.
• RY-938 Upgrade a library (Jsoup, to 1.14.3),
• RY-955 Tell the administrator if upgrade tasks aren't done. Also display the "applink ID" in a few places together with the application name, for ease of administration.

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-878 Bugfix: Make it possible to create relationships with hyphens (e.g. "relates-to"),
• RY-910 A loading icon would keep spinning after the results are displayed, when using the "upgrade" mechanism, if only 1 result was upgradable.
• RY-911 Clear the cache when the user clicks "See more" when searching for baselines.

• RY-878 Bugfix: Make it possible to create relationships with hyphens (e.g. "relates-to"),
• RY-910 A loading icon would keep spinning after the results are displayed, when using the "upgrade" mechanism, if only 1 result was upgradable.
• RY-911 Clear the cache when the user clicks "See more" when searching for baselines.

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.

• We're changing the data model to support more than 2 billion rows. We wanted to do it early in Jira, to ensure we won't have this difficulty in the future.
• It requires an upgrade task, during which Requirement Yogi is unavailable. The nominal speed is 1000 requirements per minute (by 30s batch), immediately after installation. It should be fast in Jira, since there are much fewer records. See the FAQ for more info.

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.

• We're changing the data model to support more than 2 billion rows. We wanted to do it early in Jira, to ensure we won't have this difficulty in the future.
• It requires an upgrade task, during which Requirement Yogi is unavailable. The nominal speed is 1000 requirements per minute (by 30s batch), immediately after installation. It should be fast in Jira, since there are much fewer records. See the FAQ for more info.

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.

• RY-1044 Fix a NullPointerException when processing the Confluence queue.
• RY-1044 Upgrade "minimist" (npm) and remove the dependency on Gson, which both had a vulnerability reported in their previous version.

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-1044 Fix a NullPointerException when processing the Confluence queue.
• RY-1044 Upgrade "minimist" (npm) and remove the dependency on Gson, which both had a vulnerability reported in their previous version.

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-807 The custom field for Requirement Yogi shows the spinner forever,
• RY-767 Settings in the Jira administration to delete the history of Requirement Yogi.

• RY-807 The custom field for Requirement Yogi shows the spinner forever,
• RY-767 Settings in the Jira administration to delete the history of Requirement Yogi.

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:

• RY-784 Support for deleted requirements on the Confluence side:
  • Requirements are now temporarily hidden if they are deleted in Confluence (assuming RY 2.6.5 is also installed on the Confluence side),
  • They are restored if the requirement is restored on the Confluence side,
  • It enables reimporting the page in Confluence without risking losing requirements.
• RY-787 Add a link to the app in "Manage addons"
• RY-792 Requirement text is not retrieved when set through the custom field

See Release Notes 2.6.5 for more details:

• RY-784 Support for deleted requirements on the Confluence side:
  • Requirements are now temporarily hidden if they are deleted in Confluence (assuming RY 2.6.5 is also installed on the Confluence side),
  • They are restored if the requirement is restored on the Confluence side,
  • It enables reimporting the page in Confluence without risking losing requirements.
• RY-787 Add a link to the app in "Manage addons"
• RY-792 Requirement text is not retrieved when set through the custom field.

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:

• RY-758 The UI of the Jira dialog has changed a little: Added a "Criteria" field to replace the two "Space" and "Baseline" menus, to enable an infinite number of baselines. It also allows upgrading/downgrading requirements to the provided baseline.
• RY-759 In Jira, an "Expand all" button to see the details of all requirements,

See our release notes and screenshots of the new dialog:

• RY-758 The UI of the Jira dialog has changed a little: Added a "Criteria" field to replace the two "Space" and "Baseline" menus, to enable an infinite number of baselines. It also allows upgrading/downgrading requirements to the provided baseline.
• RY-759 In Jira, an "Expand all" button to see the details of all requirements.

• RY-754 Queue: Overhaul of the timeouts for the queue in Jira. See Queue performance for all explanations.
• RY-751 Add a 30s timeout for the deletion of history items in the Jira administration, so the admin can have some feedback,
• RY-755 Fixed an upgrade task in Jira, which was causing a message in the logs.

• RY-754 Queue: Overhaul of the timeouts for the queue in Jira. See Queue performance for all explanations.
• RY-751 Add a 30s timeout for the deletion of history items in the Jira administration, so the admin can have some feedback,
• RY-755 Fixed an upgrade task in Jira, which was causing a message in the logs.

See Release notes 2.6.0.

• The custom field and the JQL function are now in general availability, even for Data Center versions,
• If you wish to use it with JQL, don't forget to set the searcher.
• See the JQL Syntax.

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.

• The custom field and the JQL function are now in general availability, even for Data Center versions,
• If you wish to use it with JQL, don't forget to set the searcher.
• See the JQL Syntax.

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.

• RY-706 Fix the "Baselines" tab in the Jira "Add links" dialog. Also, slightly improve the "Update links" process in the "Requirements" tab.
• RY-688 Notify watchers of changes to requirements (can be activated/deactiated/scoped to a group in the administration of Requirement Yogi in Jira).

• RY-706 Fix the "Baselines" tab in the Jira "Add links" dialog. Also, slightly improve the "Update links" process in the "Requirements" tab.
• RY-688 Notify watchers of changes to requirements (can be activated/deactiated/scoped to a group in the administration of Requirement Yogi in Jira).

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.

• RY-678 We have renamed the JQL function, because it collided with Xray. Please use: CustomField in requirementYogiKeys().
• RY-684 When an administrator forgets to configure the relationship for a RY custom field, if the name matches an existing relationship, then the name of the custom field will be used.

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-678 We have renamed the JQL function, because it collided with Xray. Please use: CustomField in requirementYogiKeys().
• RY-684 When an administrator forgets to configure the relationship for a RY custom field, if the name matches an existing relationship, then the name of the custom field will be used.

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.

RY-670 Clicking on the "Synchronize" button should synchronize the requirements immediately.

• RY-661 Support for the Epic field in the bulk creation of issues based on Confluence requirements. If this version is installed, you don't need to type the epic issue key in Confluence, just the epic name, and it can be templated (e.g. epic-name-{@project}).
• RY-656 Modernize the dialog to add links to requirements.

• RY-661 Support for the Epic field in the bulk creation of issues based on Confluence requirements. If this version is installed, you don't need to type the epic issue key in Confluence, just the epic name, and it can be templated (e.g. epic-name-{@project}).
• RY-656 Modernize the dialog to add links to requirements.

• https://playsql.atlassian.net/browse/RY-488 Since the JQL function requirementYogiLinks() doesn't work when there is more than 1000 issues returned, warn the user before letting them use the function.
• https://playsql.atlassian.net/browse/RY-652 For non-Data Center versions only (and Jira 8.x), ability to search using the custom field.

We will extend the second feature for Data Center customers after the performance is confirmed to be good on large instances with clusters.

• RY-488 Since the JQL function requirementYogiLinks() doesn't work when there is more than 1000 issues returned, warn the user before letting them use the function.
• RY-652 For non-Data Center versions only (and Jira 8.x), ability to search using the custom field.

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.

• RY-587 Deleting, renaming or moving an issue in Jira should send the update to Confluence.
• RY-626 Remove a cache which was outputing errors in the logs, and wasn't efficient in cluster mode.

• RY-587 Deleting, renaming or moving an issue in Jira should send the update to Confluence.
• RY-626 Remove a cache which was outputing errors in the logs, and wasn't efficient in cluster mode.

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-518 - Implement a queue from Jira to Confluence – This is the change which requires a username in Jira.
• RY-603 - Changed the storage for the connection information to Confluence (version, username and whether we auto-upgrade).
• RY-599 - In Jira, we've made it easier to set the username for the authentication to Confluence.
• RY-604 - Support for new fields for the Bulk Issue Creation: "Components", "Labels", "Assignee" and similar complex fields, and support when they are "templated" (when a component is "{@a_property}", meaning the user wants to use a property of the requirements as a component name).
• RY-553 - Stop displaying the popup when hovering over a requirement key and display it on click, to avoid flashes of popups when a user is browsing the screen with their mouse.

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-518 - Implement a queue from Jira to Confluence – This is the change which requires a username in Jira.
• RY-603 - Changed the storage for the connection information to Confluence (version, username and whether we auto-upgrade).
• RY-599 - In Jira, we've made it easier to set the username for the authentication to Confluence.
• RY-604 - Support for new fields for the Bulk Issue Creation: "Components", "Labels", "Assignee" and similar complex fields, and support when they are "templated" (when a component is "{@a_property}", meaning the user wants to use a property of the requirements as a component name).
• RY-553 - Stop displaying the popup when hovering over a requirement key and display it on click, to avoid flashes of popups when a user is browsing the screen with their mouse.

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).

• RY-511 There is a problem if requirements have been moved across spaces and they were linked to Jira. Please have a look at the bug report for more information, it requires action from the administrator.

There will be another release soon with new features, we just wanted to deliver the bugfixes quickly.

• RY-511 There is a problem if requirements have been moved across spaces and they were linked to Jira. Please have a look at the bug report for more information, it requires action from the administrator.

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

• Jira 7.13 or above (latest is 8.4),
• Confluence 6.13 or above (latest is 7.0).

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

• Jira 7.13 or above (latest is 8.4),
• Confluence 6.13 or above (latest is 7.0).

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:

• In preparation for Data Center, we've moved the storage of our issue links to Active Objects. It means there is an upgrade task. If it fails, please refer to the documentation for workarounds.
• New JQL function,
• New custom field, for customers who want to create links on the Issue Create form or make the links mandatory at any step.

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:

• RY-389 Reload the issue dynamically (after editing the links),
• RY-376 and RY-377 Fix an error when the user wasn't privileged and wanted to edit the links.

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:

• https://playsql.atlassian.net/browse/RY-256 Ability to create issues from Confluence, from a test session, and have the issue linked to the requirement that needs to be implemented.

• RY-237 Better error messages in the Jira dialog when the user is not logged in, or when the applink between Jira and Confluence isn't fully set up,
• RY-235 Update logos.

Added the ability to list the relationships between Jira projects and Confluence spaces in the Jira administration.

• RY-221 Change the search dialog in Jira for requirements, so it's easier to insert many requirements matching a query.
• RY-222 Ability to capture logs like in Confluence, to make it easier to provide debug information to the support.

The new API has a few user-facing features:

• Synchronization between Confluence and JIRA is always done as immediately as possible.
• If one app is down, it can recover and restart the synchronization in the same order.

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.

• The panel shows the same data as is sent by email to watchers.
• The panel also shows the "diff" between an old version of requirements and the new one.

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:

• It notifies watchers with the diff of the textual differences between the previous and the new requirements,
• Notifications are throttled to 3 minutes. If a user modifies several requirements in a row, they are all displayed in the same email.
• It happens whether the update is triggered in Jira by clicking "Synchronize" or by Confluence when "Immediate synchronization" is set.

• RY-131 If a Jira issue is linked with requirements from a baseline, this version gives you the ability to upgrade those requirements to a newer baseline.

RY-122 There is a wizard to rename requirements in Confluence, and it will also update links in Jira if you've upgraded to this version.

RY-138 When users have an authentication issue between Jira and Confluence, display a link so the user can manage their OAuth tokens.

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).

• Update the logos,
• When the URL of Confluence changes (move to another server, etc.), update the link of requirements.

• RY-88 Administration screen to synchronize all issues with Confluence (as a batch job).

• RY-80 Fix synchronization error when there are Applinks to other servers than Confluence.

• Fix little details for users who have an Applink but no Entity Link between the Jira project and the Confluence space. For example the synchronization didn't work if there was no entity link at all, users weren't encouraged to create an entity link and they weren't told that it still helps if they want to use baselines.
• The keyboard shortcut Alt + Shift + R didn't work in some contexts. It worked when viewing an issue and in the search/detail screen, but not in the Agile rapid boards. It now works in all contexts.

• https://playsql.atlassian.net/browse/RY-71 When Confluence is unavailable (OAuth unauthorized or disconnected), display a full explanation in the "Link" dialog.
• RY-70 Don't require a link from the Jira project to the Confluence space.

• See release notes about Baselines and Versioning
• RY-32 Baselines
• The layout of the search box was improved a bit: You can select in which spaces to search for requirements, in which baselines, and if you're an administrator there's a link to change relationship types.

Requires Java 8.

This version requires Jira 7.x.

• RY-28 Redesign the Jira dialog for link creation: Use a more conventional "Add" button, use "Remove" links to remove requirements, fix the keyboard shortcut.
• RY-57 Enable searching by space in Jira,
• Display OAuth errors more clearly, with a clickable link to re-authenticate.

Contains the same bugfixes as RY for Jira 7.x, but backported:

• RY-28 Redesign the Jira dialog for link creation: Use a more conventional "Add" button, use "Remove" links to remove requirements, fix the keyboard shortcut.
• RY-57 Enable searching by space in Jira,
• Display OAuth errors more clearly, with a clickable link to re-authenticate.

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.

• RY-61 Image and links are now accepted in requirements !
• RY-47 Fix Jira synchronization when the requirement was in a personal space.
• RY-50 Fix Jira synchronization when the issue was moved.

RY-55 Exceptions in the logs.

RY-31 Configure the type of relationships

• RY-41 The Jira-Confluence synchronization didn't work when being an Apache SSL. Cause: A semi-colon in an HTTP header, used to specify UTF-8.
• RY-27 Improve the consistency of the menu item, which doesn't work in some situations (depending on the plugin loading order).

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.

• https://playsql.atlassian.net/browse/RY-24 Confluence Questions
• https://playsql.atlassian.net/browse/RY-23 Russian, Farsi, Tamul, etc.

First version of the integration for Requirement Yogi between Jira and Confluence.