Page Comparison

...

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-529

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-518

   (and RY-562) – This is the change which requires a username in Jira.

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-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
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-592

   - We've rerun the Data Center tests for Jira after adding the queue.

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-603

   - In Jira, we've changed the storage we store connection information to Confluence (API version, username and whether we auto-upgrade).

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-599

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

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-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
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-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
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-623

   - We've improved the in-code documentation so the REST API documentation displays nicely.

RY 2.5.1

...

(Confluence and Jira)

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-587

   Added support for renamed, moved and deleted issues, to update their issue title in Confluence.

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-626

   Fix an error in Jira Data Center by removing a cache which wasn't used often.

RY 2.5.2 (Confluence only)

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-568

   Redirect to the search after renaming issues,

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-609

  Add a "Status" field in the traceability matrix for Jira issues
• RY-554 Issue not public yet.

RY 2.5.3 (Confluence only)

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-531

   Traceability matrix: A tree view for the first column, and a button to display all properties in one click.

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-634

   Traceability matrix: A column for the description of requirements,

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-630

   In the RTE, display the full details of the properties when clicking on a requirement macro,

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-628

   Small bug about the Diff screen.

In our sights

• Jira Legacy
  server Play SQL Issue Tracker serverId c44f7f6b-309d-3e24-ae45-f50de66a98eb key RY-642

   Display the lozenge when displaying dependencies in the search.