/
Merging Jira Instances with JEMH involved

Merging Jira Instances with JEMH involved

Owned by Andy Brook [Plugin People]
Mar 05, 2025
2 min read

Scenario

You are merging data from one instance to another and want to pull in related JEMH Configuration.

Summary

Key ‘configuration’ (Profiles, TemplateSets) can be migrated easily, Postfunctions and Notifications need to be redone.

What can be exported/imported

Template Sets

You can export/import these individually. Profiles and Notifications can refer templates by ID, this will break, they need to re-picking on import to whatever template is needed.

Adhoc templates can be scoped to a given project.

Profiles

Profiles can be exported to XML, singly, or if part of a group, by exporting the Default (there is an option for the full group). These profiles make reference to:

  • Project Keys

  • Issue Types

  • Custom Fields

  • Security Levels

  • Scripting references to custom fields or instance data

  • Template Sets

Projects referred in the Profile are created on import if they are missing. If you have a Jira export, then you should pre-import the necessary Projects, solve out the Custom Fields that may be used etc. JEMH Project Mappings should be reviewed, with only mappings retained that are expected in the target instance.

Issue Types are lookup by name

Custom Fields are located by exact id/type/name for Custom Fields, and re-use those fields where possible, or will use the same Name/Type, or failing that, will auto-create those fields with global scope.

Priorities are located by Name, mappings may vary if they are missing.

Scripts are not modified. Any/all hard coded references to customfield_12345 will break:

  • Script Field Processor (script references)

  • Regexp Field Processor (field mappings)

  • Script Rules

  • Custom Field Defaults

Notifications

There is no export/import capability as all custom references are to TemplateSets that have unique instance ID’s. Notifications need to be redone individually.

PostFunctions

If workflows are imported, they could refer TemplateSets on the source system, every JEMH Postfunction needs revisting to:

  • pick the appropriate TemplateSet

  • ensure custom fields that are set for To/Cc/Bcc are correct on the target instance.

Adhoc config

Global config likely will be lost in the migration, suggest finding a project, configuring it ‘like’ the source, then saving as Global.

Mail Handlers

Associate an Inbound Mail Server with a JEMH Mail Handler that identifies the Profile to use. These need adding one by one.