Mostly a technical release
2.5.0 is a major version because there are major changes in terms of internal package names and build process, but it has few immediately-visible features. Our performance tests for Data Center show no visible impact for our changes, neither for Confluence nor Jira, so in theory all should go well.
Important
| Set your credentials in Confluence | Set your credentials in Jira |
|---|---|
|
|
| What are those credentials used for? See JIRA-Confluence integration for Requirement Yogi | |
A new, public API
You are now able to program extensions to integrate Requirement Yogi with other systems!
| Public API | https://docs.requirementyogi.com |
|---|---|
| REST API | https://docs.requirementyogi.com/restapis/restapis-com.playsql.requirementyogi-2.5.0/ |
| Exemple of implementation | See our ReqIF addon, Source: https://bitbucket.org/playsql/extensions-reqif Will be published soon on the Atlassian Marketplace |
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)
- Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- (and RY-562) – This is the change which requires a username in Jira.
- - 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.
- - We've rerun the Data Center tests for Jira after adding the queue.
- - In Jira, we've changed the storage we store connection information to Confluence (API version, username and whether we auto-upgrade).
- - 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.
- - 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).
- - 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.
- - We've improved the in-code documentation so the REST API documentation displays nicely.
RY 2.5.1
- We plan to add support for renamed, moved and deleted issues, to update their issue title in Confluence.