Display Linked Issues - DC / Cloud (Connect) / Forge comparison

Cloud This page documents the Connect build of Display Linked Issues for Jira Cloud. Looking for the current Cloud app? See Display Linked Issues (Forge) for Jira Cloud.

Overview

Display Linked Issues exists in three editions:

Use this page before a move between editions - for example, from Data Center to Cloud - to see which features have a counterpart and what you need to set up again.


Legend

Value Meaning
yes Supported in this edition
no Not supported in this edition

Cells with a description say how the edition supports the feature.


Feature comparison

Feature Data Center Cloud (Connect) Cloud (Forge) - pending Marketplace approval
Jira field yes (Linked issues custom field) no yes (Linked issues custom field, issue view only)
Issue panel Right or left context, or a location you choose Web panel in the right or left context Issue panel, issue activity, issue context and issue action locations
Agile board (issue detail view) yes no no
JSM customer portal yes (the field) no no
Issue source Link types with direction; JQL Link types with direction; JQL Link types with direction; JQL
JQL placeholders ${issue.key}, ${cfValues[10100]} ${issue.<path>}, currentUser() {{ issue.key }} (templates)
Whose permissions the search uses The viewer’s The app’s The viewer’s
Issue limit 1-1000 Not configurable 1-1000 (default 50), plus rows per page
Display conditions Field context Projects and issue types of the panel Projects, issue types, Display JQL, template condition
Administration Global settings and field context Global settings Global settings and project settings
Configuration export / import no no JSON (format 1.0.0) and CSV
UI languages English English English, German
Data storage Jira database (Active Objects) Heroku Postgres, US region Forge storage (KVS) hosted by Atlassian

Moving between editions

Data Center to Cloud

Configurations move to the Forge edition with the Jira Cloud Migration Assistant (JCMA), together with the Linked issues custom fields JCMA migrates. Before you run the plan, install the Forge edition in the cloud site and put the Linked issues field on a screen of every project whose settings you want to migrate.

  • Each DC configuration of a field context becomes a configuration of the Linked issues field on the matching field context, named <field> (Data Center #<id>); a configuration shown in the issue panel also becomes a panel configuration (right column - Issue Context, main column - Issue Panel).
  • Everything arrives disabled. The description starts with Disabled after migration: ... and says what to check.
  • The link direction is kept, link types are matched by name; columns keep system fields and fields migrated by JCMA, otherwise Key, Summary and Status. The JQL is copied as text: ids are not translated, and ${issue.key} has to be rewritten as {{ issue.key }}. Max issues is at most 1000, an empty value becomes 50; Show count is not a limit in Cloud.
  • Not migrated: sub-task and system links, the panel on the agile board, the current issue in the table, exact match by a field, a custom panel location and the panel title.
  • In Cloud, linked issues are read as the viewing user. Running the migration again creates no duplicates. There is no file export for DC settings.

Details - Migrate to Cloud (DC side) and Migration from Data Center (Forge side).

Cloud (Connect) to Cloud (Forge)

The Forge edition replaces the Connect app on the same Marketplace listing; once Marketplace approves it, a Jira administrator updates the app in Apps → Manage apps. While the Connect app is installed, it saves its settings for the Forge edition on a schedule, and after the update the Forge edition creates its configurations by itself within about an hour (or right away when a Jira administrator opens Display Linked Issues settings).

  • Each Connect configuration shown in a web panel becomes a configuration with the panel’s projects, issue types and weight; a panel in the right column becomes Issue Context, in the main column Issue Panel.
  • Nothing is overwritten: a configuration whose name exists is skipped. Configurations no panel showed, with a missing link type or without a valid project are created disabled, with the reason.
  • The result is on Bulk Operations → Settings from Connect, with Import again. If no settings were found, a Jira administrator downloads the transfer file on the Connect administration page, tab Migration to Forge, and imports it there with Import from Connect file.

Details - Moving from the Connect edition. See also the Connect to Forge Migration Plan.


Where your data lives

Edition Where configurations are stored Details
Data Center Your Jira database (Active Objects) Stays inside your own Jira installation
Cloud (Connect) Heroku Postgres, US region Data Processing Addendum - Connect apps
Cloud (Forge) - pending Marketplace approval Forge storage (KVS), hosted by Atlassian Data Processing Addendum - Cloud apps

For security and compliance details across the editions, see the Trust Center, Security and the Network allowlist.