Creating a link to an existing Jira issue

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

  1. Select the option to create the link over an existing artifact.
  2. An issue selector control is displayed. Expand it to access the most recently used issues or start typing to search a matching issue by key, summary or description.
  3. Once the result set is on the drop-down list, pick an issue either by clicking on it or by pressing enter.
  4. The selected issue is displayed in a table below with its most remarkable properties plus a linking status column. The issue key is also appended to the issue selector control.
  5. If no error is reported on the Linkable column [1], [2], you can complete the selection by pressing on the Select button.
  6. You can repeat the same procedure to add more issues to link with your artifact [3] or remove them by pressing on the little cross icon, next to the issue key, in the issues' selector.
  7. Alternatively, you can click on the search for an issue using filters link to toogle the searching view for one based on applicable filters.
    On this other view, a maximum of 50 open issues will be displayed. Click on the issue you need to select. If the issue you need is not within the first 50 matching open issues, you can always search it by typing its summary or key in the with key or summary/description field, this technique can be used for rapid identification of the issue too, especially if you combine it with the two Filter combos behind; they can be used also independently and by default, they are set to display open issues. The first combo can be set to:
    User Filters are taken as template, the criteria on them may be expanded to match whatever selection you do in this form; for example, if you type something in the with key or summary/description field, this new criteria will be appended to whatever was defined in the custom filter.

    Used on its own, the first combo will apply above criteria to the default issue type [4], however, if you want to apply them to a different issue type, then use the second combo, its values match the issue types of the scheme used by the project plus the generic entry Issues to apply them to all issue types in the scheme. To confirm your selection, click on the Add button at the bottom of the page. This will add all the selected issues to the issues' selector control and to the table below [5].

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

Global Configurations Compatibility

When the OSLC Remote Application is Configuration Management enabled and it is using a Global Configuration (GC), the Linkable column will show a warning if the selected issue is not associated with the GC [6]. This will prevent the linking for Quality Management Issue resources but will still allow it for Change Requests issues [7]. Keep in mind the way an Issue is associated with a GC differs for these two latter resource types and has nothing to do with the GC-Version association made in Jira (although the Affects Version/s and Fix Version/s fields are still involved). The GC association for Quality Management Issue resources is determined by the Jira local configuration (Version) that is part of the GC: all the QM Issues having that Version set in the applicable field (depending on the actual QM resource type) will be the ones considered associated with the GC. The GC association for Change Management Issue resources, on the other hand, is determined by the Release Links of the GC: a Jira Version can be added as a Release Link on a GC and all the CM Issues having that Version set in the applicable field (depending on the link type to create this time) will be the ones considered associated with the GC. For more information click the question mark on the GC tooltip, in the Linkable column, when an Issue is not considered associated with the working GC to better understand why or what is missing.

Finally, when the OSLC Remote Application is Configuration Management enabled and it is using a GC, an additional checkbox will be displayed (checked by default), in the by-filters searching view, below the Filters area. Use this checkbox to filter the issues not associated with the GC in this searching view.

[1] The cause of the error will be visible on an auto-displayed tooltip over the Linkable column. [2] A warning can be also reported in the Linkable column, but unlike errors, these do not prevent the overall selection. [3] Except for Polarion where a known limitation allows the linking only with the first selected issue. [4] Jira project administrator can define a mapping for Collaboration Link types to Issue types; if this was done, the default display will be open issues of the type mapped by the link type being created. [5] To return from this searching view without selecting any issue, you can always click on the Go back link, at the top, or button, at the bottom, of the page. [6] An auto-displayed tooltip will notify this and, by clicking on the question mark, it allows to know why the issue is not associated with the GC. [7] All Change Request Issues can be selected for linking; however, selecting an issue which is not associated with the GC used will cause a broken/wrong backlink in Jira.