| Status | ||||
|---|---|---|---|---|
|
Our previous key suggestions system had limitation, and customers sometimes struggled with our suggestions. 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 the current page, other variants,…
For example, following the requirement CAT-002-REQ-004, we now suggest CAT-002-REQ-005 and CAT-003-REQ-001 and others matching your context.
Enjoy this new experience and feel welcome to give us feedback on our support.
| Status | ||||
|---|---|---|---|---|
|
You can now rename your requirements!
Look for you requirements through the RY search, use the checkboxes to select requirements you want to rename. We detect automatically the commons prefix and suffix that you could want to rename. You just have to check automatically that it suits your needs.
Then your requirements will be renamed, definition macros and links will be updated as well.
| Status | ||||
|---|---|---|---|---|
|
We have added the ability to search for requirements depending on the project 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.
| Status | ||||
|---|---|---|---|---|
|
Minor Improvements
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.
History UI/UX:
Display the change type in the history panel