Page Comparison

For dependencies across projects for various artifacts, the following possibilities emerge

• Dependencies between requirements
• Links to various JIRA artifacts

Regarding releases

• The scope of Releases is considered local to a project. So a release defined for one project will not be visible in another project.
• Releases defined in JIRA will be visible in projects. However, Project Manager will have to explicitly Sync RMsis with JIRA Versions.

Dependencies on requirements across projects

1. The following view will emerge, when a user clicks on the "depends on cell", corresponding to a requirement in the Requirements Tab.
2. As soon as the user selects the project, list of requirements for the project will appear.
3. User can further refine the list by choosing an option in the "Baseline dropdown list"
4. Finally the user can select the requirements from the list.

Image Removed

Requirements linked to artifacts across projects

1. The following view will emerge, when a user clicks on any of the artifact cells, corresponding to a requirement in the Traceability Tab.
2. As soon as the user selects the project, list of artifacts for the project will appear.
3. Finally the user can select the artifacts from the list.

Image Removed

1. The following view will appear, when a user clicks on the Requirement cell in the Reverse Traceability view
2. Subsequently, user can select the desired Project followed by a set of requirements.

Image Removed