Moving from the Connect Edition

The Forge edition of Display Linked Issues replaces the Connect app on the same Marketplace listing. You do not buy anything again: your subscription and license stay as they are.


Update to the Forge edition

  1. A Jira administrator opens Apps → Manage apps and finds Display Linked Issues.
  2. Click Update.
  3. Accept the permissions the Forge edition asks for - see the Permissions Reference.

Atlassian stops running Connect apps on 31 January 2027. Update before that date, otherwise the app stops working on your site. See the Connect to Forge Migration Plan for the plan across all JiBrok apps.


Configurations are transferred automatically

While the Connect app is installed, it saves its settings for the Forge edition on your Atlassian site on a schedule. After the update the Forge edition reads the settings the Connect edition saved 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 (Jira administration, Apps menu) sooner, the transfer runs right then. Nothing leaves Atlassian.

  • One configuration per panel and configuration. Each Connect configuration shown in a web panel becomes a configuration with the panel’s projects, issue types and weight, and the configuration’s name, description, link types (inward, outward or all) or JQL query, and fields in the same order, with “show name”, “show description” and “show count”. A configuration shown in several panels becomes one configuration per panel, named “<configuration> - <panel>”.
  • Where it is shown. A panel in the right column of the issue view becomes the Issue Context module, a panel in the main column the Issue Panel module.
  • Nothing is overwritten. If a configuration with the same name already exists, it is kept and the Connect one is skipped.
  • Same names. Connect configurations that share one name are all transferred: the second becomes “<name> (2)”, the third “<name> (3)”, and so on. Importing the same settings again creates no duplicates.
  • Fields. A configuration without fields shows key, summary and status. The Forge edition shows at most 50 fields: the fields after the 50th are not transferred and are named in Settings from Connect.
  • Created disabled, with the reason in the description: a configuration no panel showed in Connect (“was not shown in Connect”), a configuration with an issue link type that no longer exists on the site, and one whose panel has no valid project.

What changes

  • Panel names. The Forge edition shows configurations in its own fixed places (Issue Panel, Issue Context), so the names of Connect web panels are not kept.
  • Issue Navigator link. Show JQL link in Issue Navigator is off after the transfer.
  • Viewer permissions. Connect read linked issues as the app. The Forge edition reads them as the viewing user, so a viewer sees only the issues and fields they have access to.

Checking the result

The Settings from Connect block on the Bulk Operations tab of Display Linked Issues settings shows:

  • whether settings of the Connect edition were found;
  • when they were imported;
  • how many configurations were created, skipped or created disabled, and what to check. Configurations that were not created are listed first, each with the reason.

Import again re-runs the transfer and still skips configurations whose name already exists.

While a transfer is already running, the block says “another import of the Connect settings is running - try again in a minute”. A transfer that found the Connect settings in the middle of being saved, or ran out of time, is repeated by itself the next hour.

Then open a few issues and check that the panels show the expected linked issues.


If settings did not move automatically

If Settings from Connect says no settings were found - the Connect edition did not save them, it was already removed, or support asked you to - transfer them with a file:

  1. In the Connect edition, open its administration page, tab Migration to Forge, and select Download for Forge. Or use the file you received from us. Only a Jira administrator can download it.
  2. Open the file in a text editor and copy its whole content.
  3. In Display Linked Issues settings → Bulk Operations → Settings from Connect, paste the content into the transfer file box and select Import from Connect file. Only a Jira administrator can do this.

The result is the same as the automatic transfer: the same configurations, nothing overwritten (a configuration whose name exists is skipped), the same summary. A large file is imported in batches until it is done - keep the page open. Importing the same file again creates no duplicates.

A file of another app (“This file is for another app”), a changed file or a file that is not valid JSON is refused with the reason, and nothing is imported.


Move configurations between Forge sites

After the transfer, configurations can be exported to JSON or CSV on the Bulk Operations tab and imported on another Forge site. See Bulk Operations.


Next Steps