Creating a Jira Work Item from an OSLC Remote Application through OSLC Connect reflects the current Global Configuration, if such configuration is associated to a Jira Release. To achieve this, values for Affects/Fix versions fields are set based on the selected link type. If those fields are not part of the Work Item creation screen, Jira rejects the creation of the Work Item.
Resolution: ask the Jira administrator to add those fields to Work Item creation screen.
A Jira administrator can configure a Field Scheme to mark some fields as required. When creating a Jira Work Item from an OSLC Remote Application, the list of fields displayed in the dialog is not configurable. When a field is required but not displayed in the dialog, Jira rejects the creation of the item.
Workaround: Have users to first create the work item directly in Jira and then to select the created item using the selection dialog from the remote application. This can be enforced by configuring the corresponding Types Mapping to use Selection dialog only in Linking from Remote Applications.
Jira Cloud enables deleting remote links directly from the work item, but does not allow OSLC Connect for Jira Cloud to control the deletion behavior. If deletion is triggered directly from the Jira work item, the link is only deleted locally and the potential back-link is not deleted in the OSLC Remote Application. Only the Links Explorer can guarantee safe addition and removal of OSLC links.
Resolution: always use the Links Explorer to edit OSLC links safely and maintain consistency across OSLC applications.
When a Jira Work Item is displayed in a modal dialog in the page, dropping a URL in the OSLC Connect panel does not trigger navigation to the Links Explorer. This is due to a limitation of Jira Cloud.
Workaround: Open the work item in a full page and proceed with dropping the URL. Alternatively, if you wish to remain in the modal dialog, click open the Links Explorer in OSLC Connect panel to navigate to the page, click Add Link in the Links area and finally drop the URL in the Linking wizard.
Selecting Jira Work Items from an OSLC Remote Application shows the Reporter field of each item, with his profile photo displayed in the dialog. However, if that user chose not to share his photo publicly or if you are in different organizations, the dialog may only display his name initials. This is standard behavior of Jira Cloud.
Siemens Polarion does not support multiple submit of work items for linking. The OSLC Connect for Jira Cloud selection dialog supports selecting more than one work item for linking at the same time; however, given Polarion's limitation, only the first element of the selected work items will be linked.
Workaround: select only one work item when creating a link and repeat the creation process for as many items as there are to link.
The Change Set links discovery is no longer supported starting with DOORS Next 7.2.
For earlier versions of DOORS Next (7.0.2 and 7.1) the discovery is supported, but authentication workarounds are required.
Workarounds for DOORS Next 7.0.2 and 7.1:
When creating an external link in IBM Rhapsody Model Manager (RMM), it is possible to associate a change request (Jira work item) to it. The result is a Change Set being created and linked to the Jira work item, which should be also linked back to the Change Set, however, this is not the case. Due to a RMM limitation, the backlink on Jira is not created and only the link from RMM to Jira is created.
Workaround: none, Rhapsody Model Manager limitation does not allow a back-link in Jira.