Message Field DC - Migrate to Cloud

Message Field configurations move from Jira Data Center to Message Field for Jira Cloud with the Jira Cloud Migration Assistant (JCMA), together with the Message Field custom fields JCMA migrates. Use this page for a pre-migration assessment: it lists what JCMA carries over, which configurations are enabled in the cloud by themselves, which arrive disabled and why, and what has to be rebuilt by hand.

To move only some messages instead of a whole migration plan, download them as a file - see Download for Jira Cloud.

For a feature-by-feature comparison of the two editions, see DC vs Forge (Cloud) feature comparison.


Before you run the plan

  1. Update Message Field for Jira Data Center to 5.8.0 or later - on both lines of the app (Jira 10.x and Jira 11.3). Earlier versions have no migration path to the cloud: in 5.7.x the migration of Message Field data is switched off.
  2. Install Message Field for Jira Cloud in the cloud site before you run the plan. JCMA pairs it with the Data Center app com.jibrok.jira.plugins.message-field and shows it as the cloud app of Message Field in the app assessment of the plan.
  3. Put every Message Field custom field on a screen of every project whose configurations you want to migrate:
    • a field that is on no screen at all is not migrated - the JCMA migration log names it;
    • for a project where the field is not on a screen, the field context arrives in the cloud without that project, and a configuration of that project is placed on the global context, disabled (see After the plan).
  4. Check the Jira log. When Message Field starts, it writes to atlassian-jira.log whether JCMA can see it:
    • INFO JCMA migration listener is registered under ... will discover it if it is installed - the app is ready;
    • WARN with the reason - fix it before you run the plan;
    • WARN Field '...' (customfield_N, Message field) is not on any screen - JCMA will not migrate it... - one line for each field without a screen (step 3).

If JCMA keeps showing Message Field as an app that cannot be migrated, with no cloud app next to it, see Migration from Data Center in the cloud documentation.


Run the JCMA plan

  1. In JCMA, create a migration plan with the projects and the users you move.
  2. In the app assessment, check that Message Field shows its cloud app, and include it in the plan.
  3. Run the plan. JCMA creates a Message Field custom field in the cloud for every migrated Data Center field, and Message Field moves the configurations of these fields.

What transfers

Each Data Center message configuration becomes the configuration of the matching field context of the migrated field in the cloud. If that context already has a configuration in the cloud, the Data Center one is skipped: nothing is overwritten. The description of every migrated configuration says from which Data Center configuration it came and what was not migrated, and the Data Center settings stay next to it in the cloud configuration for reference.

Data Center setting In the cloud
Title, Body (HTML) Carried over.
Message type (Info, Warning, Error, Success, Change, Custom) Becomes the style of the message in the cloud configuration.
Status conditions (show in / do not show in statuses) Translated into the display JQL or display condition of the configuration.
JQL condition Carried over with cloud ids of the fields, projects, issue types and statuses JCMA migrated. An id with no match keeps its Data Center value, and the configuration arrives disabled.
Linked issues conditions (link type, status of the linked issue) Translated into the display JQL or display condition.
Date and time conditions (start / stop) Translated into a display condition.
Body with Velocity (Use template on) Carried over as the Data Center source; the configuration arrives disabled. Rewrite it as a cloud template - see Velocity messages.
CSS selectors Not applied in the cloud; the configuration arrives disabled.
Visibility by group or role, View for Not migrated - the cloud cannot express them yet; the configuration arrives disabled and its description names them. Replace with a JQL condition or a user-field filter.
Custom JavaScript Not run in the cloud. The script text travels with the configuration for reference only; the configuration arrives disabled.
Show as flag Not migrated; named in the description of the configuration.
Delegation (delegated roles, groups and users) Not migrated - the cloud has no delegated management; a delegated configuration arrives disabled. Who it was delegated to is not exported.
Workflow validator “Message Field: block while the message is shown” Not migrated - Message Field for Jira Cloud has no workflow validator, so the transition is no longer blocked. The JCMA migration log names each such transition.
Global settings Timeout and Show default message Not migrated; named in the JCMA migration log.
Audit log Not migrated - it stays in Jira Data Center.

Enabled or disabled

A configuration is created enabled when everything in it can be expressed in the cloud - for example, an HTML message with status and JQL conditions. It is created disabled when it uses anything marked “disabled” in the table above or a condition that could not be translated. The description of a disabled configuration starts with Disabled after migration: ... and the reason. The full list is in Enabled or disabled of the cloud documentation.


After the plan: check and enable the configurations

  1. In the cloud, open the Message Field administration page, Message Panel Settings, Panel Configurations, and find the disabled configurations - their descriptions start with Disabled after migration:.
  2. For each one, rebuild what the description names: rewrite the Velocity body as a cloud template, replace group and role visibility with a JQL condition, fix a JQL condition that kept a Data Center id.
  3. A configuration whose description says moved to the global context - no context of its projects (Data Center projects ...) was found in Cloud would show its message in every project if enabled as it is. Move it to a context of its projects first - the steps are in Configurations on the global context.
  4. Check the message in the preview and enable the configuration.
  5. For each transition the JCMA migration log names for the workflow validator, decide how to replace the check in the cloud.

Velocity messages

Data Center renders a message with Use template on as a Velocity template on the server. The cloud has its own template syntax and does not run Velocity, so such a configuration arrives disabled with its Velocity body as it was.

  • Rewrite the body with the side-by-side tables of variables, operators and recipes in Dynamic templates: side-by-side syntax and recipes. For example, $formIssue.status.name becomes {{ fields.status.name }}.
  • Some constructs have no template equivalent - inline JQL searches, $ComponentAccessor, group and permission checks in the template. The same section lists them and where to rebuild them in the configuration: Velocity-only constructs.
  • On sites with Rovo, Adapt with Rovo on the Data Center tab of the configuration translates the template for you - see Adapting Data Center settings with Rovo.

A message with Use template off is ordinary HTML: it is carried over as HTML and does not disable the configuration.


See also