Automation - Changing issue type (subtask to task) causes major bug

[Christophe Noualhat]

Hi community !! 

So I tried to create a simple automation rule, manually triggered, that would take a sub-task and change its issue type to a task.

I've seen the warning and both issue types have the same workflow.

Initial setting:
- Epic1

       - Task1

              - Subtask1

After my automation

- Epic1

       - Task1

              - Task2

Yes, you read correctly... the task type changed but the parent-subtask liaison stayed... I have an issue showing as a Task but considered by Jira as a sub-task of the original Task...

Following this, if I try to change the Task2, the only option I have is "convert to subtask" but using it gives me the error "task2 is already a subtask"

Anyone ever see this behavior ? Is this registered somewhere ? (before I open a new bug)... 

This is really annoying... we have a few hundred subtasks we wanted to convert ... (and I did not want to use a bulk update as we want to apply the epic, sprint, and other fields to the newly converted task...)

Any hint, help, experience is welcome !

Thanks ! 

[Trudy Claspill]

Hello @Christophe Noualhat 

Are you working with a Company Managed project or a Team Managed project?

What action are you using to make the change of the sub-task to task? When done through the UI while viewing an issue there is an action available to Convert to Sub-task. If you are simply updating the Issue Type field, that may be missing some of the actions taken in the background when converting an issue to a sub-task or from a sub-task.

[Christophe Noualhat]

Hi @Trudy Claspill 

I am just adding an "Edit Issue" - field : issue type action to my automation script.

Is there a better way to do it ? 

I have found a workaround but its clumsy...

1 run automation (creates the issue mentionned above)

2 search all faulty issues, bulk update them, move issues to same project, same issue type, this corrects the problem and sets the issues back on track.

As my issue is to keep the EPIC LINK from the subtask's parent, here's what I add:

At step 1, take subtask's parent's epic link and store it into a text custom field (I called it EpicLink(temp) as I'm not keeping it for long)

as a step 3, run a new automation script on the tasks and update the epic link using the content of the EpicLink(temp) field.

This works, absolutely not elegant but does the job... 

[Trudy Claspill]

You might want to open a case with Atlassian Support directly, asking if they already have an issue in their backlog for adding the Convert to Subtask/Issue feature to Automation.

[Jack Brickey]

Hi @Christophe Noualhat this rings a bell actually. let me do a bit of sleuth work and see if I can verify that.

[Christophe Noualhat]

thanks ! 

[Jack Brickey]

still digging. it is deep in my memory banks.

[Jack Brickey]

in the meantime i would report to Atlassian support.

[Jack Brickey]

@Christophe Noualhat , so I think I was off base here with my initial theory and a colleague set me straight.

the error in the automation is in your action to edit the issue. Ideally automation should give you some error but that isn’t the case and frankly would be difficult I think. Nonetheless you may wish to provide feedback to Atlassian via the in-app feedback link.

also regarding the Move that isn’t currently supported - move-an-issue-with-automation 

[Christophe Noualhat]

Hi @Jack Brickey 

What do you mean by "is in my action to edit the issue" ? 

Thanks

C

[Jack Brickey]

I was referring to your reply to Trudy…”

I am just adding an "Edit Issue" - field : issue type action to my automation script.

from that context I was assuming you were using edit issue to change the issue type which I would not expect to work TBH. Is that the case?