Skip to main content
Skip table of contents

Understanding OSLC Connect for Jira Link Storage

The following section describes how we store OSLC links in OSLC Connect for Jira. The intention is to provide support for those writing automation and migration scripts. We caution all users creating such applications. We do not directly support modification of this data and suggest both caution (careful review) and care (backups!) when working with this data.

The OSLC Links are stored as general Jira Remote Links. This allows us to use the common extension and management mechanisms. Remote links intend to enable the connection to external tools as we do in OSLC.

Note that some links do require backlinks stored in the remote tool (for example, Polarion). The storage of these links is the responsibility of the remote tool. Updating a Jira Remote link only addresses the storage in Jira and not the remote endpoint.

Accessible through REST API

Remote links are accessible via Jira REST APIs. More details can be found →

This API allows creating, updating, and deleting remote links, including our OSLC links.

A sample OSLC link stored as a remote link appears like the following.

		"id": 10203,
		"self": "",
		"application": {
			"type": "",
			"name": "Collaboration Link"
		"relationship": "implements requirement",
		"object": {
			"url": "",
			"title": "670: All exposed equipment shall have an operating temperature range of -4° to 122° F/-20° to 50° C. (In Module: Requirements for Reuse)",
			"icon": {},
			"status": {
				"icon": {}

The application type and name to be set as above to enable the behaviors of OSLC to be applied. Without the application being identified as there will be no updates of the resources, rich hovers, or icon updates.

The relationship is the role of the OSLC link. These are the standard OSLC names and are expressed in all lowercase. This is both for the relationship binding as well as the visual grouping of the links in the link view in Jira.

The URL is the remote resource location for storage in the remote tool. This will vary from tool to tool. Some tools have a standard structure using simple keys, and some, like DNG, have a more elaborate encoding.

The title is the remote artifact title. If you use the private linking mode the remote title will be stored as “”.

The application fully addresses the dynamic behavior you observe on the OSLC link. The updates after authentication are only used in the session by the UX and are not triggering updates to the Remote Link.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.