...
There is currently no automated migration tool, primarily due to differences in the data structure used for storing configuration. You will need to do ground up configuration of JEMHC.
Regions
JEMHC supports Data residency in the following regions:
US (US West)
DE (Frankfurt)
See Atlassian docs on pinning your region.
Region Migration
We have no support for region migration at this time, its a do over, its on our roadmap.
Cloud capacity plans
Your JEMHC subscription drives an allocation (1st of every month) of a Capacity Plan based on the number of subscribed (active) users; as your users increase, so does message volume and data capacity. If you consume the allocated plan, inbound mail and outbound notifications stop. No data is lost, it just remains queued.
...
Data Packs provide an on-demand short term Message and Data volume increase. Plan Upgrades provide a 1y term to gain higher capacities normally attributed to a higher number of users on a monthly basis. Both Data Packs and Plan Upgrades are purchased out of band from Atlassian Marketplace as it has not yet matured to support such app-specific metrics (see Licensing App licensing for details).
Limiting message volume usage
...
JEMHC can’t use the built-in mailbox address provided by Atlassian, so you must use an external one. When doing so you may need allow connections from the JEMHC public IP address to to your mail service. For finer grained access control, you could setup dedicated certificates that only your configuration has.
What features are missing for cloud?
Scripting support
Script Field Processor or Script Project Mapping Rules are not yet available. This is a important feature and is something we hope to offer between Q2 '23.
Jira Legacy server System JIRA serverId 31e1f342-5dce-3979-a43c-85899d565476 key JEMHC-2171
Allowlisting IP addressed used by JEMHC
Your mailhost may require JEMHC public IP addresses to be allowed. Your mailhost may have to be configured to be allowed to relay mail sending (symptoms of this are mail that doesn't deliver outside your domain).
EU and DE app data location IP addresses to allow
What's different?
Data Storage
As of MAR 2024 we support a default region of US as well as secondary DE region that new installation can pin their data to. As yet we do not have migration support from/to US deployment, potentially some areas can be manually exported (Profile JSON, templates etc) for reintroduction manually in a new DE deployment.
Inbound mail processing
JEMHC periodically retrieves mail from your configured mail servers over SSL for common protocols (POP/IMAP/EWSGraph). By default, JEMHC stores a rolling window of the last 100 mails in full (for mail under 10MB). This data is stored in the either AWS region us-east-1 (USA) or us-1 AWS region central-1 (DE) and is encrypted at-rest and in-transit. Users can opt out of email retention, but requires you to contact us to re-enable.
...
The structure of the JEMH Profile is very different from JEMHC. JEMH Profiles still have a lot of top-level configuration whereas JEMHC was designed with lessons-learned from JEMH whereby Project Mappings in JEMHC are Profile top-level feature, containing the majority of all configuration, Rules also then provide a subset of the Project Mappings.
Scripting support
Scripting support in JEMHC exists for:
Javascript PreProc Task (header manipulation)
Javascript Script Field Processor
Javascript Script Rule support in Project Mappings
Javascript Custom Field Default
The multi-tennant nature means that security is always at the forefront, and for that reason, scripts are restricted in what they can do, effectively they have access to the ‘issue' JSON structure, and the mail content where applicable, there are no remote calls allowed and no special custom functionality beyond javascript default scripting.
Messaging
Inbound/Outbound mail server connectivity isn’t within JEMH for Server/DC, in JEMHC, we have re-implemented all inbound/outbound mail server connectivity functionality. For example, JEMHC has OAuth authorization support, which requires specific admin actions to support, that cannot be migrated.
...
In JEMH Server/DC its possible to use regular expressions to match Project keys that should be handled through this particular Notification Mapping. In JEMHC, we avoid regular expressions and simplify things, enabling users to ‘pick’ all or nominated projects.
Transition Attachment Custom Field picker to allow
The Use the JEMH Transition Attachments Custom Field attachment picker for workflow transition screen has not yet been implemented in cloud, logged as:
JEMHC-3764
Status Notifications
This has not been implemented in cloud at this time.
...
For further information, see https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/72908873/Understand+how+Issue+association+works#Regexp-foreign-key-association
Public REST API
JEMHC has yet to implement a public rest API as we have for DC (Use JEMH Public Rest API to Export, Import and Update profiles ). Whilst tilted as for Profiles, we also exposed a way to deliver Mail directly over REST, which was utilised by some 3rd party email client app integrations. Those integrations will need rework once we have a public API in JEMHC. We are tracking this feature interally as
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|