Configuring Project Associations

Before users can start creating Collaboration Links from Jira to the CLM Application [1], you need to define what CLM projects will be visible to the project you manage. This is done by defining associations between your project and those in the CLM Application. Once set, the association type will define on its own the available link types to create from the Jira project to the CLM project. It is worth to mention that when creating an association, the available association types will depend in turn on the nature (domain) of the CLM Application.

This app supports the following associations and corresponding link types per application domain:

Application Domain Association Type Collaboration Link Type
Requirements Management (DNG) Provides - Implementation Requests affects requirement
implements requirement
Provides - Requirements Change Requests tracks requirement
Quality Management (RQM) Provides - Defects affects test case result
blocks test execution
tested by test case
Provides - Quality Management Tasks related test case
related test execution record
related test plan
related test script
Change Management (CCM) Provides - Related Change Requests related change request
Architecture Management Provides - Change Requests elaborated by architecture element

To create an associate with a remote CLM project:

  1. Enter to the Jira project administration page.
  2. Locate and click on the Project Associations option in the OSLC Connect section.
  3. Click on the Add Association button.
  4. Select the CLM Application in the Friend Application combo.
  5. In the Association Type combo, and by looking at the above table, select the association type depending on the outgoing link types required.
  6. As soon as you select the association type, a pop-up window will appear [2]. If you hadn't previously started a CLM Application session in the same browser, the new window will show you the CLM Application login page and you must continue with this step, otherwise please go to the next one [3]. The login page is here to complete the user authentication process, so please provide valid user credentials, it is not necessary that such user has an admin role [3].
  7. What happens after the user authentication process (or if you had already started a session in other browser's tab) depends on whether the Jira consumer was configured on the CLM Application as trusted or not. If it was configured as trusted, the only thing you need to do is to ignore a blank page that will be displayed for some milliseconds, and then you can go to the next step; otherwise, you will see the Authorize Application page which is a last confirmation to allow Jira accessing the CLM Application information on behalf the user you used to login [4]. Click the Allow button and then close the pop-up window when indicated if it is not closed automatically.
  8. Back on the Add Association dialog, a new Project field will display the available projects for the logged-in user. Choose the project to which you want to create the association and click the Add Association button.

If everything went as planned, the Add Association dialog will be closed and the new association will be displayed on the Project Associations page. You can repeat these steps to add more association types over the same or other CLM Application projects; but just remember that this time, steps 6 and 7 won't be necessary as authentication and authorization is required only once per session.

To remove an association:

  1. In the Project Associations page, locate the association you want to remove and click on the trash icon at the Actions column.
  2. Confirm your decision by clicking on the OK button in the opened Confirm delete dialog.

If everything went ok, the chosen association will be removed from the system and it will no longer appear on the table.