bulk update all subtasks to new standard issue type. without loosing parent link
Asked by Ritesh Khatri:

I have 1000+ issue are in sub-task currently. recently we have created multiple issue type on standard hierchylevel and plan to not use sub-task. we are going well on new task creation . now we need to move all sub-task to level 0 as it's parent are alredy moved to level 2.

currently we are facing loosing the parent link while transferring in bulk activity. while doing single it's going well.

I am writing to seek assistance regarding an issue we are encountering with sub-tasks in our project. Currently, we have over 1,000 issues classified as sub-tasks. Recently, we created multiple issue types at the standard hierarchy level and decided to discontinue the use of sub-tasks. We are progressing well with the creation of new tasks.

However, we now need to transition all existing sub-tasks to Level 0, as their parent tasks have already been moved to Level 2. During this bulk transition, we are experiencing a significant issue: the parent link is being lost. Interestingly, when we perform this transition for individual tasks, the parent link remains intact.

To summarize:

* We have 1,000+ sub-tasks that need to be moved to Level 0.
* Their parent tasks have already been moved to Level 2.
* Bulk transitioning causes the parent link to be lost.
* Single transitions maintain the parent link.

We would greatly appreciate any guidance or support you can provide to resolve this issue efficiently.


Answers:
author: Ritesh Khatri
body: 1. Create a Custom Field (if necessary): If you don't already have a custom field to store the parent link, create one. This field can be used temporarily to store the parent link during the transition.  
2. Set Up Automation Rules 1: Choose the Scheduled to run this periodically. specify the JQL query to select the sub-tasks (e.g., issuetype = Sub-task and project = \<YourProject\>).  
Action: Copy Parent Link to Custom Field: Add an action to Edit Issue. Set the custom field to the value of the parent link.  
For example, if you have a custom field named Parent Link, set it to {{issue.parent.key}}.  
Save Rule. Run Rule Manually  
3. Do Action Manually Using Bulk Move : Transition Sub-task to Task: Change the issue type from Sub-task to Task (or the appropriate type for Level 0).  
4. Set Up Automation Rules 2 : Choose the Scheduled to run this periodically. specify the JQL query to select (e.g., customfield_XXXXX is not empty and parent is empty and project = \<YourProject\>) Set the parent link field back from the custom field value. For example, set the parent link to {{issue.customfield_XXXXX}} where XXXXX is the ID of your custom field.  
Save Rule. Run Rule Manually


author: John Funk
body: Hi Ritesh,

You should be able to do a query on the sub-tasks, then do a bulk change, then do a Move. Then select a different parent.

comments: author: Ritesh Khatri
body: thanks for reply but i wants to be keep same parent rather than different parent. by the way i found the alternative solution


author: John Funk
body: Okay, thanks for that. I did not understand that you wanted to change them from being sub-tasks. I thought you wanted to keep them as sub-tasks and attach to a new parent.


Tags: bulk-edit

cloud

jira-cloud