I am trying to convert all my sub task into parent issue by using bulk move. However I wanted to know how can I maintain the relation/linking of those issues.
I am using Jira 3.13.
Erm. You have just said "I want to destroy the parent/child relationship, but I don't want to destroy the parent/child relationship". I'm not 100% sure what you're looking for here.
My best guess is that you probably want to set up an issue link type called "was child of", and link each child to it's parent before doing the change to parent issue types. There's no easy way to do this though, you'll have to manually link each one, or script something to do it for you.
Ok, well, the parent will still be recorded in the history, so you could rely on that. If you need it on-screen, then I'm afraid the manual linking will be needed.
Another option just sprang to mind though - if you've got the script runner plugin, or a bit of coding knowledge, you could write up a derived/scripted field that can look in the history and pull the previous parent ID out to be displayed. No need for links or data amendments then.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs