Very often, a user is browsing Jira issues and OSLC Remote Application artifacts in different browser tabs, why just don't drag and drop them into the Jira issue for linking? This is possible with the Dropping dialog for the following applications:
In order to use this dialog, make sure to select the
Drop existing radio in the
Link dialog and click the
Open dropping dialog button. Once opened, this dialog has two modes to work with:
click to pastelink.
Back to dropbutton.
The most versatile mode is the native mode, as it also accepts artifact URLs either by pressing
Ctrl + V (assuming they were
previously copied to the clipboard) or by dropping them (whenever they were draggable in the remote application). Second mode is more for cases
when users want to edit the copied URL before processing it, that's why it contains an
Accept button to indicate when the
pasting/editing action(s) ended and processing must start.
Both modes are capable of processing multiple artifacts or artifacts URLs at once, there's no need for a user to drag or copy one element at the time unless the OSLC Remote Application does not provide a mean for multiple selection.
There are two main validations a dropped/pasted element must pass in order to enable the linking with the Jira issue:
If these validations are not met, for any single dropped/pasted element, the whole linking will be prevented (by disabling the
no matter if other elements were accepted. Rejected elements come first on the results table and they are identified by a red cross icon and a below
rejection-cause message. Accepted elements are identified by a green check-mark icon and users can hover them to get a small preview of the artifact.
Users can remove rejected (and accepted) elements from the results table by hovering them and pressing the gray cross icon at their right. Keep in mind
no linking has been performed yet, removing elements from this table only means user is not longer interested in linking to them. Final linking will be
performed with remaining non-rejected elements when pressing the
From where to drag or copy an OSLC Remote Application artifact depends on the specific remote application:
When a Global Configuration has been configured on the Jira issue, there is a third validation dropped/pasted elements must pass to be accepted:
Being compatible means that if both configurations are not the same, the one used by Jira takes precedence and the remote artifact
must be valid (exists) there or it will be rejected. When an artifact is accepted under this condition (mismatching configurations) the icon on the results table is
a warning icon and includes a legend explaining linking is accepted but warns the user about final artifact version used on the issue may be different from the one
dropped/pasted. If user accepts this situation, linking can be continued as having warnings on results table does not disable the
Given each remote application has it's own way to deal with configurations or not at all, this point is revisited on each individual application topic above.