We used JCMA to move our large production projects over, it seems even though SubTasks are enabled. They are not being split off and made into their own jiras, related to the original issue.
Why does this happen, and how can i resolve this. It seems to be every project we moved over as far as being reported.
Any direction would be great. Also have a support ticket open trying to understand this.
Hello @RJ Denicola
What version of JCMA did you use?
What version of Jira did you migrate from?
What happened to the subtask issues during migration? You said they weren't "split off". Does that mean that the subtask issues were not migrated at all and don't exist in your Cloud environment?
Did you review the log files generated by JCMA for the migration to see if they reveal any useful information about the subtasks?
Was this your test migration? Did you open a support case with Atlassian as part of your migration planning to have them engaged, or are you working with an Atlassian Solution Partner?
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.