Migration from Data Center

Configurations of Message Field for Jira Data Center move to the cloud with the Jira Cloud Migration Assistant (JCMA). To move only some messages, import a Data Center export file instead.

JCMA recognizes Message Field for Jira Cloud as the cloud version of the Data Center app (com.jibrok.jira.plugins.message-field): in the app assessment of the migration plan, Message Field shows its cloud app, and its data migrates with the plan.


Before you run the plan

  • Message Field for Jira Data Center - the first Message Field Data Center version released after 5.7.1, or later.
  • Install Message Field in the cloud site before you run the plan.
  • Put the Message Field custom field on a screen of every project whose configurations 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. A configuration of such a project then has no context of its projects in the cloud, so it is placed on the global context and created disabled (see Configurations on the global context).

What is carried over

  • Each Data Center field configuration becomes the configuration of the matching field context of the migrated Message Field custom field (the Custom Field module).
  • Nothing is overwritten: if the field context already has a configuration in the cloud, the Data Center one is skipped.
  • A configuration whose custom field JCMA did not migrate as a Message Field field of this app is skipped; the JCMA migration log names the Data Center field.
  • The JQL condition of a configuration is carried over with cloud ids: ids of Data Center custom fields (cf[10100], customfield_10100), projects, issue types and statuses inside it are replaced with the ids JCMA migrated them to; names and keys stay as they are. If an id has no match in the migration (the field, project, issue type or status was not migrated), the condition keeps the Data Center id, the configuration is created disabled, and its description names the id - fix the JQL before you enable it.
  • 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 created disabled, so the message is not shown in every project until an administrator decides.
  • The description of a migrated configuration says when and from which Data Center configuration it was migrated and what was not migrated.

Enabled or disabled

A configuration is created enabled when everything in it can be expressed in the cloud. It is created disabled when it uses:

  • Velocity;
  • custom JavaScript;
  • CSS selectors;
  • visibility by group, role or “view for”;
  • delegation;
  • a display condition that could not be translated;
  • a message over 20000 characters.

Velocity. A message is treated as a Velocity template only when its Data Center configuration has useTemplate = true. With an empty value the message is ordinary HTML and is carried over as HTML - it does not disable the configuration.

The description of a disabled configuration starts with Disabled after migration: ... and the reason.

After the migration, review the disabled configurations, rewrite what was not migrated (for example Velocity as templates, see Templates) and enable them. JavaScript in messages is not available in the cloud.


Configurations on the global context

A configuration placed on the global context is listed in Message Panel Settings, Panel Configurations, disabled. Its description 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, if any, follow after a ;. Enabled as it is, the configuration shows its message in every project that uses the global context of the field. To show it 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 Message Field and the context of these projects.
  3. Enable the imported configuration and delete the disabled one on the global context.

Moving individual messages with a file

JCMA moves the whole instance by a migration plan. To move only some messages - when you move in parts, try the cloud first, or need a few configurations - import the Data Center export file instead:

  1. In Message Field for Jira Data Center, open All Message fields settings, select the configurations and click Download for Jira Cloud. Custom JavaScript, delegation and the audit log are not included in the file.
  2. In the cloud, open the Message Field administration page, Bulk Operations tab, Import, and paste the content of the file. Only a Jira administrator can import it.
  3. The preview lists every message of the file by field and context name, with what does not carry over (the same list as a JCMA migration) and whether it will be created disabled. Select the messages to move.
  4. On the Field and context step, choose for each message the Message Field of this site and its context, or Do not import. A field with the same name is pre-selected; the file names the projects and issue types of each context, so a context of the same projects and issue types is pre-selected too. The global context is never chosen for you, and a message without a chosen context is not imported.

The rules are those of the JCMA migration:

  • a context that already has a configuration is not overwritten;
  • a message is enabled only when everything in it can be expressed in the cloud - otherwise it is created disabled, the reason first in its description;
  • statuses and link types of display conditions are matched by name;
  • a JQL condition is carried over as text - ids of Data Center fields and projects inside it are not translated, check it after the import;
  • importing the same file again creates no duplicates: a message already imported is reported as such.

A configuration of the Custom Field module in a cloud export file goes through the same Field and context step when imported on another site, and keeps its display condition. See Bulk Operations.


See also