Is it possible to Migrate sub task to task issue type while maintaining parent link

Johnathan June 13, 2024

Hi Community of Jira enthusiasts!

I am bulk editing  & migrating sub tasks into tasks and the parent link field gets cleared, is it possible to change the issue type without losing the parent field? ( 1000's or issues to manually relink it epic, it is to disruptive for the production environment)

If so, what setting would prevent this?  Permission etc?

Crossing my fingers this is workable!

Best,

Johnathan

 

 

2 answers

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 13, 2024

Hello @Johnathan 

No, you cannot convert a subtask to a level 0 (standard) issue type and keep its parent set to another level 0 (standard) issue type.

Jira does not allow an issue to have a parent that is at the same level. The parent issue must be in the level above the child.

The Issue Type Hierarchy indicates which issue types are at which level.

1 vote
Ritesh Khatri
Contributor
July 13, 2024
1. Create a Custom Field : 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 Automation 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. Bulk move Manually : Transition Sub-task to Task: Change the issue type from Sub-task to Task (or the appropriate type for Level 0).
4. Set Automation 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.

 

do follow sequance will work. it's worked for me well

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events