Hi Everyone,
Thank you for previously raising this bug and bringing it to our attention.
With the release of Jira Cloud Migration Assistant (JCMA) 1.7.3 on September 12th, 2022, and our ongoing commitment to improving our product, we have transitioned to a new code base.
With this ticket having been logged before the changeover date/JCMA version, we believe it’s no longer relevant to the current code base. Bearing that in mind and continuing the culture of being honest and open, we have taken the decision to close this bug at this time.
If you feel this bug is still impacting your team, please let us know through the Migration Support channel and we will revisit the issue.
We appreciate your understanding and look forward to providing you with an enhanced migration experience.
Thank you again for providing valuable feedback!
The Migrations team
Hi Everyone,
Thank you for previously raising this bug and bringing it to our attention.
With the release of Jira Cloud Migration Assistant (JCMA) 1.7.3 on September 12th, 2022, and our ongoing commitment to improving our product, we have transitioned to a new code base.
With this ticket having been logged before the changeover date/JCMA version, we believe it’s no longer relevant to the current code base. Bearing that in mind and continuing the culture of being honest and open, we have taken the decision to close this bug at this time.
If you feel this bug is still impacting your team, please let us know through the Migration Support channel and we will revisit the issue.
We appreciate your understanding and look forward to providing you with an enhanced migration experience.
Thank you again for providing valuable feedback!
The Migrations team