Creating a Jira issue before linking to it

Continuing with the steps defined on the parent topic...

  1. Select the option to create the link over a new artifact.
  2. Fill out the form with the issue data [1], [2], only Summary and Issue Type fields are required [3].
  3. Click on the Create button to create the new issue and then the new link to it.

If everything went as planned, the dialog will be closed and you will see the new link created on the links section.

Next time you start an OSLC Remote Application session and get to a page where Collaboration Links exist, you will be prompted to authenticate yourself and authorize the Jira collaboration before you can start seeing detailed information on the link.

[1] You will see the form only if the license for OSLC Connect for Jira is still valid. Otherwise, you will see this message: OSLC Connect for Jira license is not granted: followed by the specific license issue message. If this is the case, please contact your administrator. [2] If tabs were defined on Jira for the create issue screen, they will be displayed here too. [3] Jira project administrator can define a mapping for Artifact types to Issue types; if this was done, the Issue Type field will be filled automatically with this mapped issue type.

Global Configurations Compatibility

When the OSLC Remote Application is Configuration Management enabled and using a Global Configuration (GC), either the Affects Version/s or Fix Version/s field will always be visible [1], [2] and filled automatically with the Version corresponding to the GC used. Keep in mind the way this Version is determined is different for Quality Management Issues and Change Management Issues. The Version to use for Quality Management Issue resources is the one corresponding to the Jira local configuration that is part of the GC. The Version to use for Change Management Issue resources, on the other hand, is the one associated with the GC but through the Release Links so make sure this link exists on the remote application's GC and not only in Jira Versions'. It is highly recommended you do not change this value so a "compatible" issue can be created for the link. If no compatible Version is found/used for linking, a warning will be displayed for Change Management Issue resources and the linking will be still allowed; an error and no linking-allowed will be the case for Quality Management Issues resources.

[1] The actual field used is determined by the Issue Resource type, if it is a Quality Management one or the Link type being created if it is Change Management one. [2] It will be always visible even if it is not included in the create issue screen.