Managing Jira versions on Global Configurations

Starting IBM Engineering Lifecycle Management (ELM) 7.0.2, the way how backlinks were discovered in ELM applications changed. [1] Summarizing, now both, the Jira version and the Global Configuration (GC) must be linked to each other. This can be perfectly done by Jira [2] when creating a GC-Version association as long as the IBM Global Configuration Management (GCM) user used by the Jira project administrator has the Add or remove links privilege. If this is the case, they do not require help from you to keep Jira versions and GC's synchronized. On the other hand, if their GCM user lacks this privilege, you will be required to synchronize the GC with the Jira version every time they create, update or remove a GC-Version association.

Associating a Jira version on a Global Configuration.

Preconditions:

Procedure:

  1. Open a component or configuration; then, click the Links tab and click Edit.
  2. Click Add Link and select the Release link type.
  3. On the opened Add Releases dialog, open the From combo and select the target Jira project. [5], [6]
  4. Select one or more versions to add, and click Select.
  5. Click on the Save button.

If everything went OK, the Jira version will be listed below the Release type and, hovering it, will display a small preview of it.

Dissociating a Jira version from a Global Configuration.

  1. Open a component or configuration; then, click the Links tab and click Edit.
  2. Locate the version to dissociate and hover its row.
  3. Click on the cross gray icon on the right.
  4. Click on the Save button.
Quality Management and Xray Support.
Jira projects having issue types mapped to Quality Management resources (Test Case, Test Plan, Test Execution Record, Test Script and Test Result) require, besides the above, to add the Jira Configuration (Version) to the Global Configuration as described below. Do not forget Jira Versions are considered local Configurations for Quality Management.

Adding a Jira Configuration (Version) to a Global Configuration.

  1. On an open component or configuration page, click on the Add Configurations... link.
  2. In the Add Configuration dialog, open the first combo and select the OSLC Connect for Jira application [7].
  3. In the Project combo, select the Jira project to use.
  4. Optionally, switch the Stream combo to Baseline to fetch released Versions only.
  5. Optionally, type a pattern to find Versions with it in the Type to search names input field.
  6. Select the Configuration/Version to add and click on the Select button.

If everything went OK, the dialog is closed and the Jira Version is now listed as a local Configuration in the Global Configuration. To remove a Jira Configuration, just perform the regular steps to remove any other local Configuration from the Global Configuration.

[1] See the Synchronizing Jira Versions with ELM Global Configurations topic for details. [2] Through OSLC Connect For Jira app. [3] Ask the Jira administrator to ensure this. He/she can review the topic Configuring Consumers for TRS for details. [4] This can be done by trying to add a Jira project association from the GCM project area admin page. The process is completed when Jira projects are listed. [5] All Jira projects on which the user used during the authentication process has the Browse Projects permission will be visible by default. [6] To limit the Jira projects listed here, follow the steps of Limiting version links by enforcing project area associations topic. [7] If the application is not listed, make sure the GCM consumer is marked as trusted in Jira and a suitable functional user is set on it and try again.