Linking development plans

For plans in two project areas, you can link those plans so that you can view the status of both plans in your project area. You can also link to a plan that is in another installation of EWM.

1. In the Plan editor, click the Links tab.
2. Click the down arrow next to Add Link.
   • To link to a master plan, select Contributes To Plan.
   • To link to a plan that is a subset of the master plan, select Tracks Plan.
3. Optional: In the Add Link window, select another project area that contains the plan. You must link both of the project areas. If no project area is linked, this window is not shown.
4. In the Plan window, enter the name of the plan to link to.
5. Select the plan and click OK.

Typically for a software project after the business analyst creates a requirement collection, the project manager creates a development plan. To ensure that the project manager correctly captured the requirements in the development plan, the business analyst can link the plans. Linking plans ensures that the business analyst sees both the requirements and the development plans.

1. In the Plan editor, click the Links tab.
2. Click the down arrow next to Add Link, and select Implements Requirement Collection.
3. In the Add Link window:
   1. Click the name of the location for the existing requirements collection.
   2. Select Link to existing, and click OK.
4. In the Collections Selection page, select the requirements collection:
   Note: In this example, the artifact format is a Collection. You can also link to a Module artifact format using these steps.
   1. Type the name of the requirements collection in the search field. Alternatively, you can search for the requirements collections in the Filter Display by Folder field. Type the name of the requirement that you want to search for in the filter field, and options appear in the artifacts field:

      The requirements collections display in the Select artifact field.

   2. In the Select artifact field, select the requirements collection, and click OK.
5. Click Save.

After the development plan is created, the test manager can create a test plan. Because testing starts after a feature is developed, the test manager can link both of the plans to check status of the features.

1. In the Plan editor, click the Links tab.
2. Click the down arrow next to Add Link icon (), and select Tested by Test Plan.
3. In the Add Link window:
   1. Select the project area to link to.
   2. Select Link to existing or Create New.
   3. Click OK.
4. In the Select Test Plan window, select the checkbox of the plan to link to, and click OK.
   Tip: To search for a plan, type the plan name in Type Filter Text.
5. Click Save.
   Learn more about linking artifacts: To link a development plan to another development plan in IBM Engineering Workflow Management, a test plan in IBM Engineering Test Management, or a requirement collection in IBM Engineering Requirements Management DOORS® Next, do one of the following operations:

   • Drag the development plan icon of the plan editor onto the target artifact. To see the Create links dialog box, drop the artifact on the drop target displayed. Select the link type and click Create links.
   • To copy a link in the plan editor, click Copy Link icon . View the target artifact and click the Paste As Link icon . In the Create links dialog box, select the link type and click Create links.
   • To copy a link by using keyboard shortcut, view the development plan to be copied and press the following keys:
     • For Windows or Linux, Ctrl+C
     • For Mac, Command+C
     To paste the link, view the target artifact and press the following keys:
     • For Windows or Linux, Ctrl+Shift+V
     • For Mac, Command+Shift+V
     In the Create links dialog box, select the link type and click Create links.

   Restriction: When you create a link by using drag-and-drop or copy-and-paste method, you cannot perform the following actions:

   • You cannot create links when the source and target artifacts are viewed in different browsers. The target artifact must be viewed in a tab or window of the same browser as the source artifact.
   • You cannot create links if the user-selected Configuration Context in the source is not the same as the configuration in the target application.