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:
- Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.Test & Compliance module: Can now work without Requirement Yogi,
- Jira: Activate the custom field by default,
- Jira: The issue is reindexed when the custom field is modified,
- Bug when creating a baseline and a page was in draft,
- Coverage matrix: Ability to work cross-spaces,
- Scaffolding compatibility: Pages are now reindexed when a Live Template is updated,
- Traceability matrix export to Excel: Requirements are now links, so it is easier to navigate between Excel and Confluence,
- Library upgrades (technical issue without user-facing feature),
- Removal of the "display mode" in the RY Report macro.
Resolved in 2.6.2
- Main improvement: Overhaul of the timeouts for the queue in Jira. See Queue performance for all explanations.
- Add a 30s timeout for the deletion of items in the Jira administration, so the user can have some feedback,
- Fixed the upgrade task in Jira, which was causing a message in the logs,
- Ability to delete the requirements which were on an Excel file, when the Excel file was removed.
- Fix the traceability matrix for Safari,
- Fix the space tree for IE,
- Fix the link to the definition of requirements, which was malformed.
Resolved in 2.6.3
- In the Jira dialog, changed the UI to allow an infinite number of baselines (see screenshots). Added a "Criteria" field to replace the two "Space" and "Baseline" menus, to enable an infinite number of baselines. It also allows upgrading/downgrading requirements to the provided baseline.
- In Jira, an "Expand all" button
- Add a separate role to rename requirements
- In the baseline refreeze, the "Add dependency" button only added the examples, not the whole list of dependencies. This also enables more requirements in a refreeze
- Fix the export-to-Excel function, which requires a specific version of a library
- Traceability matrix: Ability to use a traceability matrix for the baseline blueprint, so customized columns can be displayed
- Traceability matrix: Ability to change the owner
- Traceability matrix: Support for the "single select" custom field in Jira
- Traceability matrix: Support for the "multiselect" custom field in Jira
- Traceability matrix: Display "Load more..." when it is needed