This question is in reference to Atlassian Documentation: Configuring sub-tasks
Yes and no.
If your two issues are in the same project, then converting XYZ-123 to be a sub-task of XYZ-456 will work fine, and it will retain the key of XYZ-123.
If you are moving it across projects though, then no, it will need to take on the project key of the new project and get a new number. You'll still be able to find it by searching for the old key.
Also, bear in mind that if XYZ-123 has its own sub-tasks, you'll need to decide what to do with them - they'll need to be moved to another parent, converted to be parent-level issues, or even deleted (ugh).
Hi Arumugam.
If main taks A-1 and B-1 bellong to different project, then when A-1 is converted to subtask of B-1 it can´t mantain same identifier (because A and B are the project keys)
But if your question targets to mantain the "trasability", keep in mind that though A-1 once converted is not A-1 any more, it doesn't loose the reference, I mean, if you look for A-1 you´ll find it, no matter it actual identifier now was B-x
Regards, Aylin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.