Change task parent to new issue when issue is moved
Problem
Moving issues closes the original issue and creates a new issue. Child items remain attached to the original issue, however this behavior seems counterintuitive as that's no longer the "working" issue.
Proposal
When an issue is moved, all child items that also live within the same location should be moved along with the parent.
- Move Issue: Close and clone
- Move Task: Change the namespace from the old to the new, change the parent from the old issue to the new issue
Fringe case: If an issue (or future work item type) has children and those children live in a different location than the work item being moved, do not move those children, but retain the parent/child relationship once the parent item is moved to the new location.
Potential solutions
- Option A: The tasks get moved to the same project as the moved issue.
- Option B: The tasks stay in the original project but retain their relationship with the moved issue.
- Option C: The ability to select either Option A or Option B at the time you're moving the issue.
- Option D:
insert the ideal behavior here
Edited by Gabe Weaver