Skip to end of metadata
Go to start of metadata

Requirement Yogi is generally built to support copying and moving.


Product Requirement Document blueprint,

Dictionary blueprint,

or any page with requirements.


If you copy pages with requirements, then you end up with 2 definitions of the same requirement.

  • Replace definitions with links,
  • Or copy the page to another space.


If you move to another space, the URL of the requirements it contains will change.

  • All pages referencing those requirements will be updated,
  • JIRA issues will only be updated at the next synchronization (or immediately if you've configured your integration with immediate sync).
  • A redirect will be created between the old URL and the new URL.





The copy will be reset, so you can freeze it whenever you want.


If you move a baseline, it will keep all its properties and frozen requirements.

RY Test Session blueprint


The copy will have all tests in the same status as the source page.



As a rule, if you feel like the requirements were not properly indexed, either edit the page or go to the tools menu, at the top-right of the page:

Just going to this page will check that requirements exist and aren't duplicated. You can also click "Refresh requirement descriptions" and even use this screen to transform all references to those requirements on the space to actual links!



  • No labels