I'm receiving an error stating "Jira Work management is not available on your cloud site" while Migrating a set of (Software + Business) Projects from Jira Server to Atlassian Cloud using JCMA. Why it is blocking the migration with this product, As my source (Jira Server) doesn't have this Product.
And I'm able to create the Business type Projects in Cloud without the Jira Work Management.
Why it is forcing me to add the Product to the Site, which incurs additional cost for the Product in billing..
The Jira Work Management pre-flight check has been added in v1.7.3 of the Jira Cloud Migration Assistant.
If you have Business Projects or Users and Groups with product access to Jira Core in your Migration plan then you have two options to pass this check successfully.
If neither of these is an option for you, please reach out to support.
Why did we add this check?
One of the top error codes we've observed in our monitoring has been permission errors due to missing products such as JWM. If you disable this pre-flight check with the dark feature flag, you will ignore the pre-flight and likely fail after the migration has completed.
We figured it is better to have this information up front and correct before finding out after.
Regarding my last question, I got an answer here, and it was a very positive one:
"Jira Software and Service Management are built on top of Jira Work Management. If you have a license for either Jira Software or Service Management, you also get Jira Work Management with project templates made specifically for business teams. The Jira Work Management plan you inherit depends on what plans you have for your other Jira Cloud products."
That's correct @Rob , apologies for not seeing your question earlier. However, the way the check is running at the moment it needs JWM specifically provisioned under the billing subscriptions. Best thing to do at present is to activate a JWM trial on your target instance, run your migration and then deactivate if no longer required.
In the next release of JCMA, we will downgrade the severity of this check to be non-blocking. Some customers have expressed feedback that they would prefer the migration to fail at run-time instead of pre-flight.
Side note: If you are migrating to a Sandbox site, we can't provision JWM directly so the check will become blocking and you must work around it.
Only impacts Premium and Enterprise customers as Sandbox is not available on the Standard Plan. If you are affected by this - please review the workaround on this Bug report. https://jira.atlassian.com/browse/MIG-1169
Jira Work Management is the base product for Jira Cloud, so it will not incur a separate cost if you already have Jira Software.
You should open a support ticket with Atlassian if you have not already. Please post back here with the resolution so others will know.