Set your credentials in Confluence	Set your credentials in Jira
What are those credentials used for? See Requirement Yogi for Jira - Basically it was required for the best performance, to ensure we support multinode environments and the Data Center requirements.

A new, public API

You are now able to program extensions to integrate Requirement Yogi with other systems!

Unofficial support for ReqIF and other formats

In the next few weeks following RY 2.5.0, we'll publish a plugin which uses our Public API and imports 80% of a ReqIF document.

Note: We won't officially "support ReqIF" because it would require us to support 100% of the ReqIF specification, and most documents exist in other formats than ReqIF. The goal of the plugin is to show how external documents can be supported, and thus make it possible for you to import your own document and do the mappings yourself.

Queue in Jira (a username is required)

Since we've implemented the Jira bulk issue creation for requirements, we've seen issues for users who create more than 2,000 issues and want to keep them in sync.

• A queue in Jira will allow us to reliably notify Confluence of changes (issue rename, issue move, etc).

• The drawback is that it requires a username in Jira's administration.

Minor versions

RY 2.5.0 (both Confluence and Jira)

• RY-529 - Getting issue details... STATUS

• RY-518 - Getting issue details... STATUS  (and RY-562) – This is the change which requires a username in Jira.

• RY-616 - Getting issue details... STATUS  - We've changed the internal storage for saved traceability matrixes. They should be transferred automatically using a background job that runs 3 minutes after the plugin is installed; If they are not migrated automatically, you can click "Migrate now" in the traceability matrix dropdown.

• RY-592 - Getting issue details... STATUS  - We've rerun the Data Center tests for Jira after adding the queue.

• RY-603 - Getting issue details... STATUS  - In Jira, we've changed the storage we store connection information to Confluence (API version, username and whether we auto-upgrade).

• RY-599 - Getting issue details... STATUS  - In Jira, we've made it easier to set the username for the authentication to Confluence. The ticket will remain "open" until we do the same in Confluence.

• RY-604 - Getting issue details... STATUS  - In Jira, support values sent by RY Confluence for the "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 - Getting issue details... STATUS  - In Jira, stop displaying the popup when hovering over a requirement key. Instead, display it when we click on the requirement, to avoid flashes of popups when a user is browsing the screen with their mouse.

• RY-623 - Getting issue details... STATUS  - We've improved the in-code documentation so the REST API documentation displays nicely.

RY 2.5.1 (Confluence and Jira)

• RY-587 - Getting issue details... STATUS  Added support for renamed, moved and deleted issues, to update their issue title in Confluence.

• RY-626 - Getting issue details... STATUS  Fix an error in Jira Data Center by removing a cache which wasn't used often.

RY 2.5.2 (Confluence only)

• RY-568 - Getting issue details... STATUS  Redirect to the search after renaming issues,

• RY-609 - Getting issue details... STATUS Add a "Status" field in the traceability matrix for Jira issues

• RY-554 Issue not public yet.

RY 2.5.3 (Confluence only)

• RY-531 - Getting issue details... STATUS  Traceability matrix: A tree view for the first column, and a button to display all properties in one click – See our new screenshots of the Traceability matrix!

• RY-634 - Getting issue details... STATUS  Traceability matrix: A column for the description of requirements,

• RY-633 - Getting issue details... STATUS  Traceability matrix: A column for the name of the original page of the requirement.

• RY-630 - Getting issue details... STATUS  In the RTE, display the full details of the properties when clicking on a requirement macro,

• RY-628 - Getting issue details... STATUS  Small bug about the Diff screen.

• RY-643 - Getting issue details... STATUS  Disable the search box in the RY Report macro, since no-one uses it.

• RY-642 - Getting issue details... STATUS  Display the lozenge when displaying dependencies in the search.

• RY-641 - Getting issue details... STATUS  Sort the links by alphabetical order - in the popup, in the search, in the reports etc.

• RY-635 - Getting issue details... STATUS  Display the space name when searching for requirements in Confluence's Quick Search.

RY 2.5.4 (Confluence only)

• RY-554 (Unofficial) Support for the UTF-8 keys in the rename and the refreeze.

• RY-600 - Getting issue details... STATUS  Upgrade the "refreeze baseline" experience. Use drag'n'drop, support UTF-8 requirements,

• RY-621 - Getting issue details... STATUS  In the popup, display the status of Jira issues,

• RY-645 - Getting issue details... STATUS  For the popup, let the administrators configure whether the popup should be displayed immediately or upon click,

• RY-647 - Getting issue details... STATUS  When exporting a page to PDF, if there was an RY Report macro displaying a diff, the diff wouldn't be coloured. Added the colour.

• RY-646 - Getting issue details... STATUS  Entirely remove the code that used to notify administrators when the communication queue with Jira failed,

• RY-584 - Getting issue details... STATUS  Decouple the global limit, let the users set the limit for the pages, import, and so on.

RY 2.5.7 (Confluence and Jira)

• RY-595 - Getting issue details... STATUS  Personal queue. There are messages between Confluence and Jira which can sometimes fail (authentication, etc). The user who modified the requirement page gets notified (randomly once every 50 views) and they can retry messages.

• RY-650 - Getting issue details... STATUS  Confluence administration: The administrator can check whether they are reaching a high number of used IDs in the database.

• RY-472 - Getting issue details... STATUS  Confluence administration: An "Uninstall" screen helps customers leave Requirement Yogi by uninstalling all the macros.

• RY-607 - Getting issue details... STATUS  Space administration: Ability to purge trashed requirements.

• RY-636 - Getting issue details... STATUS  Diff: PDF exports should contain the strikethrough when elements are removed.

• RY-488 - Getting issue details... STATUS  Jira: Users are warned when using the JQL function with too many requirements.

• RY-652 - Getting issue details... STATUS  Jira (8.0 and above, and non-Data Center only): We have a new syntax to search for requirements.

RY 2.5.8 (Confluence)

• RY-657 - Getting issue details... STATUS  Add logging for an error that is displayed in the traceability matrix,

• RY-655 - Getting issue details... STATUS  Display a tab in the administration with a few usage statistics.

RY 2.5.9 (Confluence and Jira)

• RY-662 - Getting issue details... STATUS  We've noticed that baseline numbers could collide in certain circumstances. Introduce a cluster-wide lock to avoid this.

• RY-661 - Getting issue details... STATUS  Jira bulk issue creation: Support for the Epic field.

• RY-658 - Getting issue details... STATUS  Traceability matrix: Description column didn't display when the report was inserted in Confluence pages.

• RY-654 - Getting issue details... STATUS  Diff: Include reverse dependencies when doing a diff on dependencies.

• RY-664 - Getting issue details... STATUS  Ability to clean up broken links (Go to space administration → RY Reindex),

• RY-665 - Getting issue details... STATUS  Error in the editor when inserting requirements (interference with another app).

RY 2.5.10 (Confluence)

• RY-589 - Getting issue details... STATUS  Traceability matrix - 1. Better "save" menu, 2. They can be cross-space, 3. They can be made visible to the whole space.

• RY-663 - Getting issue details... STATUS  Traceability matrix: The expand/collapse box works on pages.

• RY-668 - Getting issue details... STATUS  Display the results of the last queue job, in the administration.