Configuring Link Types to Issue Types mappings

This is an optional but very useful configuration. It is optional because if you do not perform it, OSLC Connect for Jira will still be functional; however Jira users may have to perform additional steps every time they create incoming links. To better understand this configuration, let's speak first about the Collaboration Links types.

As explained in the Configuring Friends and Consumers topic, Collaboration Links can be created either from Jira or the CLM Application. Available link types depend on the nature (domain) of the CLM Application; this means users cannot create the same link type between a Jira issue and a DNG Requirement or an RQM Test Case, users will create for example an "implements requirement" link between a Jira issue and a DNG Requirement, but will create a "tested by test case" link between the same Jira issue and an RQM Test Case. Now, saying "a Jira issue is tested by a test case" does not sound very well, it does not make sense to say an issue is tested... fortunately, Jira allows users to define custom issue types in a way they could say "this feature or improvement is tested by a test case". It is quite likely your company has already define custom issue types and it would be good if, by the time users create Collaboration links between CLM Application and Jira, they could scope the custom issue types that has meaning for the link type they want to create.

By setting this configuration, you will be able to define a mapping between the available link types and the Jira issue types defined in a scheme. If your company defined a scheme shared by multiple projects, you only have to define this mapping once, otherwise you will have to define a mapping per scheme used in a project [1]. To define a Link Type to Issue Type mapping you need to:

  1. Enter to the JIRA ADMINISTRATION > Manage apps page.
  2. On the left panel, click on the Link/Issue-Type Mapping option in the OSLC Connect section.
  3. Select the scheme for which you want to define a mapping in the Scheme combo.
  4. A table with three columns will be rendered. Available link types are in the middle column and are the same for all schemes. In the first column are the corresponding CLM Application artifacts to which the link type has meaning. Finally, in the last column, you can customize or restore the Jira issue type that will be mapped to this link type. This disposition of columns was chosen so you can easily set a mapping by creating a simple sentence like "Requirement Implemented By Feature" or "Requirement Affected By Bug". To customize a mapping, click on the Customize link to enable the combo next to it and you can choose the issue type defined in such scheme.
  5. Repeat last step for other link types until you have defined all required mappings.
  6. Click on the Save button located at the top right corner of the page.

Having defined this mapping, next time CLM Application users want to create a Collaboration Link, OSLC Connect for Jira will preselect the issue type according to the chosen link type in this mapping [2]. If no mapping is defined at all for a link type, or you have restored your customization, OSLC Connect for Jira will use the default issue type, defined on the scheme, to preselect the issue type when creating a Collaboration Link. To restore a mapping customization:

  1. Locate the mapping on a scheme you want to restore.
  2. Click on the Restore button located in the last column.
  3. Click on the Save button located at the top right corner of the page.