/
Release 2.6 – Library upgrades

Release 2.6 – Library upgrades

Mostly a technical release

2.6.0 is a major version because we have upgraded a lot of our libraries. There is slightly-higher-than-usual probability of breaking with some versions of Confluence/Jira, although we have tested every major version.

The custom field is available by default in Jira

In Jira, the "Requirement Yogi Links" custom field was only available to non-Data-Center versions by default. It is not available for everyone.

  • JQL works!

    • Example: RequirementCustomField = 'REQ-002' (the name depends on the name you provided for this field),

    • Example: RequirementCustomField in requirementYogiKeys("REQ-%")

    • See: JQL Syntax

  • If you have already created a custom field, you need to upgrade the "searcher" to be able to use JQL. See screenshot below.

New layout for the Jira dialog

As highlighted in Jira links, we have refactored the Jira dialog to accomodate for an infinite number of baselines:

 

Removed

  • We have removed the "display mode" field form the RY Report macro, since it didn't work and no-one noticed it for 2 years.

  • In the traceability matrix, it is not possible anymore to display the status of a Jira issue in the same cell. You must add a new column for the "status" field.

More issues resolved in 2.6.0

In order of relevance:

Resolved in 2.6.2

Resolved in 2.6.3

Resolved in 2.6.5



Related content

Release 2.1 – Ambitious bugfixes
Release 2.1 – Ambitious bugfixes
More like this
Release notes 2.2.5 for Jira
Release notes 2.2.5 for Jira
More like this
April 2024
More like this
Release 2.3 – Jira issue creation and traceability matrix
Release 2.3 – Jira issue creation and traceability matrix
More like this
July 2024
More like this
JQL Syntax and Extensions
JQL Syntax and Extensions
More like this