Display Linked Issues - Forge edition

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.

Update to the Forge edition

The Forge edition of Display Linked Issues ships on the same Marketplace listing as the Connect edition. To move to it, open Manage apps in Jira and click Update on Display Linked Issues. You do not buy anything again and you keep your license.

Atlassian ends support for Connect apps on 31 January 2027. See the Connect to Forge Migration Plan for the plan across all JiBrok apps.

From the day the Forge edition is published, the admin page of the Connect edition shows a Forge edition is available banner with a Migration plan link to that page.


Your Connect settings

While the Connect app is installed, it saves its settings for the Forge edition on your site on a schedule. After the update the Forge edition reads them and creates its configurations by itself, within about an hour - nobody has to open the settings page. If a Jira administrator opens Display Linked Issues settings sooner, the transfer runs right then. Nothing leaves Atlassian.

  • The result appears in the Settings from Connect block on the Bulk Operations tab: whether settings were found, when they were imported, how many configurations were created, skipped or created disabled, and what to check. Import again re-runs the transfer and does not overwrite configurations that already exist.
  • If no settings were found, a Jira administrator downloads the transfer file in the Connect edition - its administration page, tab Migration to Forge, Download for Forge - and pastes it into Settings from Connect with Import from Connect file.

How Connect records become Forge configurations

Connect Forge edition
Each pair “web panel × configuration” One configuration; a configuration shown in several panels becomes “<configuration> - <panel>”
Web panel location Right Issue Context display location
Web panel location Left Issue Panel display location
Configuration not attached to any web panel Configuration created disabled (“was not shown in Connect”)
Record with an unknown link type or an empty project Configuration created disabled, with the reason
Web panel weight Order within the display location
Configurations with the same name All transferred: “<name> (2)”, “<name> (3)”
Configuration without fields Shows key, summary and status; at most 50 fields are transferred

Web panel names are not migrated, and the Issue Navigator link is off after the transfer. Details - Moving from the Connect edition.


What works differently on Forge

Whose permissions are used

The Connect edition read issues as the app. The Forge edition reads issues as the person viewing the page, so each user sees only the linked issues they have permission to see. There is no “actor” setting in this edition - the server rejects it.

Display locations instead of web panels

Instead of one web panel per record, you choose one of four display locations:

  • Issue Panel
  • Issue Activity
  • Issue Context
  • Issue Action

The Connect weight becomes the order of configurations within a location.

Admin page

The admin page is organized into Configurations, Bulk Operations and Modules. Modules are labelled with the name Display Linked Issues.

Options not in this edition

If a configuration or an import file contains an option the Forge edition does not support, the server rejects it on save and on import.


Next steps