Linking artifacts across projects

Owned by Deepak Jangid (Deactivated)
Jun 12, 2019
2 min read

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 an option to
    • explicitly Sync RMsis releases with JIRA Versions.
    • OR automatically sync, if configured so by the Administrator.

Regarding Test Cases

  • In the current version of RMsis, the Test Cases are assumed to be written for the Requirements specified for the current project.
  • Hence links to Test Cases across Projects are not available as on date.

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.

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.

  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 and Baseline; followed by a set of requirements.