Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Public APIhttps://docs.requirementyogi.com
REST APIhttps://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

...

  • Jira Legacy
    serverPlay SQL Issue Tracker
    serverIdc44f7f6b-309d-3e24-ae45-f50de66a98eb
    keyRY-616529
  • Jira Legacy
    serverPlay SQL Issue Tracker
    serverIdc44f7f6b-309d-3e24-ae45-f50de66a98eb
    keyRY-592518
     (and RY-562) – This is the change which requires a username in Jira.
  • Jira Legacy
    serverPlay SQL Issue Tracker
    serverIdc44f7f6b-309d-3e24-ae45-f50de66a98eb
    keyRY-623-616
     - 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.
  • Jira Legacy
    serverPlay SQL Issue Tracker
    serverIdc44f7f6b-309d-3e24-ae45-f50de66a98eb
    keyRY-603-592
     - We've rerun the Data Center tests for Jira after adding the queue.
  • Jira Legacy
    serverPlay SQL Issue Tracker
    serverIdc44f7f6b-309d-3e24-ae45-f50de66a98eb
    keyRY-599603
     - In Jira, we've changed the storage we store connection information to Confluence (API version, username and whether we auto-upgrade).
  • Jira Legacy
    serverPlay SQL Issue Tracker
    serverIdc44f7f6b-309d-3e24-ae45-f50de66a98eb
    keyRY-529599
     - In Jira, we've made it easier to set the username for the authentication to Confluence.
  • Jira Legacy
    serverPlay SQL Issue Tracker
    serverIdc44f7f6b-309d-3e24-ae45-f50de66a98eb
    keyRY-518
     and 
    604
     - 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).
  • Jira Legacy
    serverPlay SQL Issue Tracker
    serverIdc44f7f6b-309d-3e24-ae45-f50de66a98eb
    keyRY-562-553
     - 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.
  • Jira Legacy
    serverPlay SQL Issue Tracker
    serverIdc44f7f6b-309d-3e24-ae45-f50de66a98eb
    keyRY-604
    Jira Legacy
    serverPlay SQL Issue Tracker
    serverIdc44f7f6b-309d-3e24-ae45-f50de66a98eb
    keyRY-553623
     - 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.