Page Comparison

...

1. The operation will create a new Id for Requirements in the new project.
2. System will maintain link to source requirement in the back end.
3. The hierarchy will be preserved, depending upon the user preference.
4. The attachments will also be copied.
5. Linked Artifacts are ignored at this point of time.
6. If another copy of a requirement already exists in the target project, the system will return an error.

User Interface

1. Notes and Recommendations
   1. It is highly recommended that all the desired requirements should be exported in one single operation. It is easier to delete a requirement in the target project than iterating through the process.
2. The requirements export process is described below:
   1. Use multi-select to select all Requirements you wish to export.
   2. Choose "Export Requirement" from the Table Menu.
   3. When prompted , enter the name of target project, plus one of the desired options mentioned below
      1. Append to the bottom of the list including hierarchy information (default).
      2. Identify the location to paste the requirements and exclude hierarchy information.
   4. Make your choice, fill in the details sought and choose "Export".
   5. When you select the target project, you will see the entire set of requirements inThe selected requirements and their hierarchy will be appended to the Planned Requirements table of target project.