| Info |
|---|
Introduced in 1.7. See the product page |
You've wrote written your requirements, but now there's a problem: you want to change one or more requirements' requirement key. Let's start by selecting the requirements to rename.
...
The system is intuitively simple, yet powerful: ticking Ticking the box next to "Key" will select all requirements in the current space, even those who are not shown if your number of requirements exceed the display limit. You can then uncheck tick boxes to exclude requirements from your search. Or you can check particular tick boxes to select only these requirements. You can even combine this with the Search Query: start Start by performing a search with the Search Query (for For example, let's say we want requirements beginning with "TECH" : key ~ 'TECH%' ; see See Search Syntax for more informations about the Search Query), then if you tick the checkbox for all requirements, only those from the query will be selected. This allows you to refine your queries easily.
...
This wizard allows you to entirely rename a requirement, just type the new key you want and Requirement Yogi takes care of everything for you: obviously Obviously every occurrence of this requirement is changed in your documents, and the dependencies are modified as well. Even your JIRA issues are updated, if you have linked your Confluence instance with JIRA and installed Requirement Yogi on JIRA.
...
If an error occurs, it will appear at the bottom of the screen. As the status indicates, "No modification was saved", your requirements are safe. This behaviour behavior can yet be problematic if the error is thrown from JIRA, as the link between Confluence and JIRA is not error-prone. For example, you can have an authentication error. Moreover, if you delete your Application Link, Requirement Yogi keeps a trace of the links in JIRA, just in case you will recreate your Application Link. This is useful, but in case of renaming, it will test the connection with JIRA and fail. This is why we added a check box "Ignore JIRA errors" in the renaming wizard. If you tick it, JIRA errors will be displayed as warning and will not cancel the renaming task (other errors still cancel it). However, if you choose to ignore JIRA errors and an error occurs, your JIRA issues won't be updated. Thus, your requirements links in JIRA will be incorrect, and you will not be able to synchronise them (because they have been renamed, in the JIRA point of view it is no longer the same requirement) and you will have to remove the former links and add the new manually.
...