...
| Info | ||
|---|---|---|
| ||
Requirement Yogi lets you rename requirements in batch. It also synchronizes the new names with JIRA. See the product, Requirement Yogi. |
You've written your requirements, but now there's a problem: You want to change one or more requirement key. Let's start by selecting the requirements to rename.
...
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 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.
Renaming multiples Requirements
...
Please note that this task can take a while if you rename many requirements, so be patient. The progress bar is updated frequently and automatically to inform you about the progress of the task, as well as the status under this progress bar. Please also note that the "Time remaining" is only an estimation and can be inaccurate.
Once it's done, a button named "Acknowledge" appears. Click on it to be redirect to the Requirement Yogi Search screen. This is the recommended way, rather than using the menu bar, as this also tells Confluence to stop tracking the task.
...
You can also cancel the task, by clicking on the "Stop and cancel" button at the bottom of the task status page.
Limitations
| Warning | ||
|---|---|---|
| ||
Requirement Yogi won't be able to rename and move requirements which are located in Scaffolding's live templates. Technically, RY edits the XHTML source of the wiki page, so RY can only help with moving and renaming if requirements stored in "ContentEntityObjects". If you proceed, you will find:
|
...