Configuring Artifact 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 and the artifact types involved; this means not all link types are suitable for linking two given artifacts. A DNG requirement having an "affected by" link to Jira, for example, would be expected to have a Defect or Bug artifact on the other side, it would not make sense to find a Task artifact instead of it. Generic artifact types have been defined as suitable for linking between different domain applications and, with OSLC Connect for Jira, those belonging to Change Management domain are now supported: Defect, Implementation Request, Quality Task and Requirement Change Request.

By setting this configuration, you will be able to define mappings between generic expected artifact types and Jira issue types defined in a scheme, in a way that next time creating a link from a CLM Application requiring a Defect on the other side, the corresponding Jira issue type can be preselected by default. 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 an Artifact 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 Artifact/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 two columns will be rendered. In the first column are the generic and expected artifact types. In the second column, you can customize or restore the Jira issue type that will be mapped to this artifact type. 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 artifact 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 artifact type in this mapping. If no mapping is defined at all for an artifact 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.