Requirements are unique per space, and we use key suggestions to help you number your requirements. When you create REQ-001, we’ll be able to suggest the next following requirement → REQ-002.
| Status | ||||
|---|---|---|---|---|
|
...
When you create and delete a requirement, we still remember the last created key.
For example, even though REQ-003 is deleted, we’ll still suggest REQ-004, and you’ll have to bypass the insertion (when adding the macro, click on Insert twice) to add REQ-003
...
Use Cases
When using the Transformation Wizard, and rules like the Key Generation: if
If you generate requirements, then delete some of them, and decide to reuse the key generation rule, we will still generate requirements with the last created key, whereas you might like to start
from the last deleted requirement.
How to reset key suggestions
| Status | ||||
|---|---|---|---|---|
|
In the Requirement Yogi tab > Administration > Key Suggestions
...
See the list of requirements already created in the space, an example with the current value for the numbering.
For SYRS- requirements, you can see that the next requirement to be created with this key will be SYRS-10
If you want to set a specific value for the next suggestion, click on the current value.
If you want to reset the key suggestion to zero, click on ‘Reset’
If you want to delete a key suggestion, click on ‘Delete’