Our previous key suggestions system had limitations. So we stepped back and built a new system filling the gaps of the previous one.
You will still be able to define any type of key you want, and suggestions will be based on your input, other requirements in the page, and across your space and variants.
For example, with the requirement CAT-002-REQ-004, we now suggest CAT-002-REQ-005 and CAT-003-REQ-001.
You can also find your key suggestions in the Requirement Yogi Manage section.
Find all key suggestions per variant
Reset keys to the last existing number
Delete key suggestions
Find more information in the docs. Enjoy this new experience and feel welcome to give us feedback on our support.
In Confluence, when using the search, you can now search for requirements depending on the Jira links project’s they belong to.
For instance project = ‘PROJ’ will only return requirements that are linked to Jira issues in the ‘PROJ’ project.
Head to the Search syntax page to learn more about how to search for requirements.
In the Coverage tab, you can now select a requirement and check it’s coverage with Jira issues. You can filter with the relationship, type, and project.
Jira:
The Jira requirement panel no longer shows all baselines of the requirements when filter is not specified
Fixed the missing description in requirement link preview
Requirement Detail:
We now render the Atlassian emojis in requirement description and properties
Traceability Matrix:
Changed the name of the column ‘Variant’ to ‘Variant / Baseline’ as it displays both information.
Improved the rendered Jira fields: ‘Linked issues’ and ‘sub-tasks’.
Baselines:
Improved the UI/UX of the ‘Select requirements’ screen upon freezing requirements.
Modification Matrix
When using the ‘Modified only', we’ve now included requirements that were added or deleted between one version and another.
History UI/UX:
Display the change type in the history panel