This page is aimed to IBM Engineering Requirements Management DOORS Family users to let them know which elements can be drag/copied and drop/paste into the OSLC Connect for Jira Dropping dialog for linking, as well particularities that application have using this dialog.
In DOORS client, users can drag requirements directly from a Module and drop them in the Dropping dialog, alternatively they can right-click on any of
them and select the
Copy URL option to paste it then on Jira .
By default, it is not possible to drag and drop more than one requirement at once, no matter if it is possible to select more than one, only the one
from the dragging started is going to be dropped on the Dropping dialog, this is due to a limitation of the DOORS client itself. Fortunately,
OSLC Connect for Jira comes with a DOORS add-in to workaround this, ask the DOORS administrator to install it and once
done, a new
OSLC Connect menu will appear on the open Module window. Then, to copy and paste multiple requirements' URLs at once :
Shift+Clickto select the last one.
OSLC Connectmenu and select the option
Copy Selected Object Urls.
DOORS Web Access (DWA) users have only one way for linking using the Dropping dialog :
Attributespanel on the right, expand the
URLattribute and right-click on the link.
Up to version 9.7.1, there is no difference between using a Global Configuration on Jira issue or not, the same elements discussed above are suitable to be drag and drop or copy and paste in the Dropping dialog. This is due to the nature of the DOORS application and because it does not support Configuration Management at all.
Starting 9.7.2 version, DOORS modules can work in the context of a Global Configuration, this means that the third validation about global configurations mentioned in the parent topic (i.e. being the same or compatible configuration rule) applies: if the dropped/pasted requirement does not exist in the configuration used by Jira, the linking will be rejected. The elements from where the dragging can start are the same, however it is worth to mention that only the current version URL is carried for dropping. In other words, no matter if you were dragging a baseline requirement, you will end up with the current version requirement once dropped. The workaround to this situation is to use the copy/paste approach, this way the versioned requirement URL is used and then you can create unidirectional  links from Jira issues to baselines requirements .