Migration from Data Center

Settings of Display Linked Issues for Jira Data Center move to the cloud with the Jira Cloud Migration Assistant (JCMA), together with the Linked issues custom fields JCMA migrates. Nothing leaves Atlassian.

There is no file path for Display Linked Issues: settings move only with a JCMA migration plan.


Before you run the plan

  • Display Linked Issues for Jira Data Center - the first Display Linked Issues Data Center version released after 3.4.0, or later.
  • Install Display Linked Issues in the cloud site before you run the plan.
  • Put the Linked issues field on a screen of every project whose settings you want to migrate. JCMA carries over the projects of a field context only for the projects where the field is on a screen: for any other project the context arrives in the cloud without that project, and the configuration of the field for that project is placed on the global context (see Configurations on the global context).

What is transferred

Each Data Center configuration of a field context becomes:

  • A configuration of the Linked issues field on the matching field context of the migrated field, named <field> (Data Center #<id>): a context of the same projects, narrowed by issue type; a global Data Center context goes to the global context. A configuration limited to projects that have no context of the field in the cloud (the projects were not migrated, the field was not on a screen of these projects, or they have no context of their own) is placed on the global context, and its description says so.
  • A panel configuration, when the Data Center configuration was also shown in the issue panel. A panel in the right column becomes Issue Context, a panel in the main column Issue Panel; the projects and issue types of the field context limit where it is shown, and the panel weight is kept.

Both keep:

Data Center setting In the cloud
Link direction (inward, outward or both) Kept.
Link types Matched by name. “Every link type” becomes every link type of the cloud site. A link type with no cloud type of the same name is named in the description.
JQL query Copied as text. Ids of Data Center projects and fields inside it are not translated, and Data Center placeholders such as ${issue.key} have to be rewritten as templates - for example {{ issue.key }} (see Data Sources).
Table columns Kept in the same order: system fields and custom fields migrated by JCMA. A column with no cloud field is dropped and named in the description. When no column is left, the table shows Key, Summary and Status.
Max issues Kept, at most 1000; an empty value becomes 50.
Show count Not a limit in the cloud: the description says Show more after N rows: Cloud has no "Show more" and shows up to N linked issues.

Everything is created disabled

Every migrated configuration is created disabled. Its description starts with Disabled after migration: ... and the reason or what to check, then says from which Data Center configuration and context it was migrated and what was not migrated. Review the configurations in Display Linked Issues settings and enable them there.

  • Nothing is overwritten. If the field context already has a configuration in the cloud, the Data Center one is skipped.
  • Running the migration again creates no duplicates. Configurations already transferred are reported as such; a configuration changed or deleted by an administrator since is left as it is.

Configurations on the global context

A configuration of the Linked issues field placed on the global context has a description that starts with, for example:

Disabled after migration: moved to the global context - no context of its projects (Data Center projects 10100, 10200) was found in Cloud

The numbers are the ids of the Data Center projects of its context; other reasons follow after a ;. Enabled as it is, the configuration shows the linked issues in every project that uses the global context of the field. The panel configuration of the same Data Center configuration is not affected: it keeps the migrated projects. To show the field only in its projects:

  1. In Jira, give the field a context for these projects: add the projects to a context of the field or create a new one.
  2. In Bulk Operations, export the configuration and import the file. On the Field and context step, choose the Linked issues field and the context of these projects.
  3. Enable the imported configuration and delete the disabled one on the global context.

Not migrated

  • Sub-task and system links - the cloud issue view has no such links.
  • The panel on the agile board.
  • Include current issue - the current issue in the table.
  • Exact match by a field (Matching issues).
  • A custom panel location - the panel is shown in Issue Panel.
  • The panel title - cloud panels have a fixed title.
  • The “Show more” button: Data Center showed the first rows of the table and folded the rest under it. The cloud table has no “Show more” button and shows linked issues up to the limit of the configuration - 50 by default, which you can change in the configuration settings.

Each one is named in the description of the configuration that used it and in the JCMA migration log.


Viewer permissions

Data Center checked permissions on the server. The cloud edition reads linked issues as the viewing user, so a viewer sees only the issues and fields they have access to.


See also