Upgrading JEMH to v4.x.x
The requirement to upgrade to JEMH v4.x.x for Jira 9.x compatibility is that you must be using JEMH 3.3.18+ (ideally 3.3.latest), with Jira 8.x.x:
To get to Jira 9 you must go through Jira 8: → jira 8.x → jira 9.x
To get to JEMH 4 you must go through JEMH 3.3.18+jemh 3.3.17 or Lower → jemh 3.3.18 + → jemh 4.x.x
Profile Import in 4.x.x
JEMH 4.x.x is a major release change that includes significant breaking changes. Profile exports from JEMH 3.3.x cannot be imported into 4.x.x as we have removed a quantity of legacy support present in the JEMH 3.x.x series. In order to recover your 3.3.latest Profile configuration you will need to restore your Jira 8.x.x Jira instance from backup, upgrade JEMH to 3.3.latest then upgrade to Jira 9.x.x again. Once correctly upgraded, you can export the Profile XML (from 4.x.x) and import into your main Jira as usual. This approach doesn’t solve the database problems caused by not following the upgrade path above.
Failure to upgrade through 3.3.x
Failure to follow the above upgrade path will lead to database inconsistencies that prevent JEMH from starting/functioning - old upgrade tasks have been removed in 4.x.x.
All support queries for this scenario will be directed to this page. There are only two remedies:
a) Happy Path
Start your upgrade path again, using Jira 8.x.x with JEMH 3.3.latest, then upgrade Jira to 9.x
b) Unhappy Path
Failure to follow the upgrade path has impact. We do no provide support to ‘fix’ databases that have partial schema updates applied. The only remaining remedy is to completely remove all JEMH data and start again. The exact methods of removing database tables vary by database. As a starting point, see https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/2850865.
If you have not first upgraded to JEMH 3.3.latest please see the following: