Configuring Project Associations

Before users can start creating Collaboration Links from Jira to the OSLC Remote Application [1], you need to define what OSLC Remote Application projects or artifact containers will be visible to the project you manage. This is done by defining associations between your project and those in the OSLC Remote Application [2]. Once set, the association type will define on its own the available link types to create from the Jira project to the OSLC Remote Application 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 OSLC Remote Application.

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

Application Domain Association Type Collaboration Link Type
Requirements Management Provides - Implementation Requests affects requirement
implements requirement
Provides - Requirements Change Requests tracks requirement
Quality Management 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 Provides - Related Change Requests related change request
affected by defect
affects plan item
contributes to
Architecture Management Provides - Change Requests elaborated by architecture element

To create an association with an OSLC Remote Application project or artifact container:

  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 OSLC Remote 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 [3]. If you hadn't previously started an OSLC Remote Application session in the same browser, the new window will show you the OSLC Remote Application login page and you must continue with this step, otherwise please go to the next one [4]. 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 [4].
  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 OSLC Remote 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 OSLC Remote Application information on behalf the user you used to login [5]. 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 Artifact Container field will display the available projects for the logged-in user [6]. Search and/or choose the project/artifact container to which you want to create the association and click the Add Association button [7]. Searching is done by typing a text on the Search container by name input field [8], this causes that all projects/containers that do not contain the typed text be hidden from the picker field.

If everything went as planned, the Add Association dialog will be closed and the new association will be displayed on the Project Associations page including the remote project name, friend application URL context and enabled link types. You can repeat these steps to add more association types over the same or other OSLC Remote 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.

Associating with IBM Engineering Requirements Management DOORS Family 9.7.2 containers
If the OSLC Remote Application is DOORS Family, version 9.7.2 or higher, and Jira users are planning to use Global Configurations (GC), be aware that choosing the right container matters.
Regular Jira users may have a different experience, when trying to link to a DOORS Family requirement, depending on whether the project association was done with a module, a folder or a project...
This is derived from the fact that Jira behaves differently depending on whether the remote application is GC-enabled or not, and for DOORS Family 9.7.2 and above, this is determined at container level and not at application level according to the following table:
ContainerIs GC-Enabled
ModuleDepends on the Module configuration itself.
The use case of major impact of this is a user trying to link to a module that is NOT GC-Enabled but being rejected by Jira because user forgot to set an Affects Version/s or Fix Version/s (a GC validation). User will be wondering why a GC is requested if module is not GC-Enabled, and the reason is that the project association was done with the module's containing folder (or project) which is always considered as GC-Enabled from Jira's perspective. To avoid this kind of problem, the recommendation is to always associate directly with the module if this is not GC-Enabled.

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.