We support OSLC Connect on both the Jira Cloud and Jira Data Center. While our OSLC Connect for Jira Cloud is a complete OSLC Solution, some features our customers know and love are not yet available on Jira Cloud.
The following features are not currently available in OSLC Connect for Jira Cloud. This will be updated as new releases address these differences in features. Unless otherwise noted, all features are on the existing product roadmap.
Link Type Version Mapping
In OSLC Connect for Jira Data Center, a project could customize whether the Fix Version or Affects Version field is used to set the GC context for a link. The current release supports this configuration in a text file, rather than the UX experience in DC. This will be delivered in the upcoming months.
Type Mapping & Link Restrictions
As an enterprise feature, we have supported the ability to customer the OSLC usage on Jira types for a Jira Scheme. This meant you could identify which Jira Issue type would be used for a specific ELM use case (for example, Defect). As well you could control the allowable links from that Jira resource type. This will be delivered in the upcoming months.
QM(XRay) Support
In Data Center, we allow the mapping to OSLC QM types. This allowed XRay users to map their XRay Jira items to testing types. This enabled the linking and reporting features natrually availalbe between Xray artfacts and Requirements. In addition we supported shape and QM TRS feeds to enable IBM Report Builder Reporting. This is targeted to be available by the end of the year.
Approvals
A unique feature for IBM DNG is to approve a changeset with a workitem. We allow customizing these rules of what consitutes an approval in our Data Center product. This will be delivered in the upcoming months.
OSLC Query
Our OSLC Query behavior has some limitations in capability in responding to all possible queries. The behavior of this API will continue to be improved.
Resource Shape Customization
Resources shared via OSLC APIs only have standard attributes. We will be adding similar functionality to extend resources to include admin-selected additional attributes.
Friend Rehosting
In Data Center, we had automated the process of retargeting a Friend (Repository connection) to a new location. This is a likely future inclusion.
TRS Participation Check
In Data Center, we allowed an Admin to check is a resource had been added to the TRS feed and when it was last updated. This will be delivered in the upcoming months.
Custom Rich Hover Previews
In Data Center, we allowed users to configure their rich hovers with Jira Screens to customize the content. This feature is under review whether it will be added to Jira Cloud.
This information is provided to guide your Jira Cloud migration. If you have specific questions, clarifications, or critical requirements, please create a support ticket so we can provide clarity.