More > Link > Collaboration Link.
Out of the box, a Jira issue can be linked to other issues, Confluence pages, or external web pages. Once OSLC Connect for Jira is installed (and configured), another kind of links can be created: Collaboration Links. These links relate the issue with ALM applications' artifacts (the OSLC Remote Application artifacts). The link relationship is determined by the Collaboration Link type and these are determined by the remote project associations.
If no errors occurred, or all failed results are discarded, the
Link dialog is closed,
then the created link will be visible in the
Issue Links area. Once a single issue link
is created (not necessarily a Collaboration Link), you will be able to start the
Issue Links section, by pressing on the plus icon located at the top-right corner of
the section. If the link created is a Collaboration Link, you can create more links of the same type,
by dragging and dropping remote artifacts on the Collaboration Link type section.
Issue Linksarea, choose the specific link you want to remove.
If everything went ok, the dialog will be closed, the link is removed from the system, and it will no longer appear in the
Issue Links area.
If, on the other hand, you see the
Failed to remove the back link dialog, please contact your administrator in order to check the communication with the OSLC Remote Application,
or any other issue before continuing. At this point, the safest is to click on the
Cancel button and wait for a resolution.
The current GC is determined by the following steps/settings:
Affects Version/sor the
Users can track these settings, with actual values for their linking issue, by clicking in the branches icon next to the GC title. It's worth mentioning that this GC resolution process is not performed only within the linking wizard, it's the same procedure taking effect when displaying Collaboration links created already, this means:
Last but not least, what occurs when a Jira issue is set to work with a Global Configuration but requires linking with artifacts of projects that don't? The answer depends on the remote project and its level of Configuration Management support. Applications not being compatible at all may just ignore the context information sent by Jira and the linking will work. Others, like IBM Engineering Requirements Management DOORS Next, where Configuration Management can be supported but it's actually disabled, will deny the linking; so all will depend on the remote application accepting or not the linking.