We have a user that has requested for a set of issues from a source project to be moved to a new destination project. Both projects share the same project configuration. When we attempted to run a bulk update of the issues, we were informed by the application of the following:
You are not allowed to bulk move sub-task issues together with their parent issue. In this case, you will only be asked to move the sub-task if you move the parent issue to a new project.
When we chose the destination project, the application is obviously unable to locate the parent ticket for these sub-tasks as it has not been successfully created.
In this particular scenario, what would the proper steps/process be to allow for the parent issues and their corresponding sub-tasks to be moved properly? Please advise.
I believe if you create a search for only the parent issues, and then go through the Bulk Change > Move process then the sub-tasks will be moved along with their parent issues. Jira does not support having a sub-task in a different project than its parent issue.
You need to make sure that the sub-tasks really are Sub-task type issues, and not some other generic issue type that has simply been named "sub-task"
I would recommend that you try moving just one or two parent issues known to have sub-tasks and confirm that the sub-tasks are also automatically moved.
Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events