Subtasks get assigned to Epic

[Le Clue]

Hi. So for our one project we are using an Active sprint for our devs and today for some reason after a few years, when they move a subtask along, then it loses it's parent and gets assigned as a subtask to the epic.

Not exactly sure what is happening so looked at the automatons and nothing was being triggered there. Ialso had a look at the Workflow Post Functions and everything still has the deault settings.

Has anyone else experienced this or know what is causing this?

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Your question is might have two interpretations, but the answer is the same for both.  When you say "the issue loses its parent and gets assigned as a sub-task on the Epic", do you mean:

• The sub-task is converted to a base-level issue which then takes on the Epic as its parent.
• The sub-task is still a sub-task type, but it has moved from being part of a base-level issue to being part of an Epic.

In both cases though, the answer is simple - one of your humans moved it from the old parent issue.

[Le Clue]

Hi Nic

Thank you for the quick response.

So interpretation 2 is the corect one.

Unfortunately, it is not a human as it happens instantly and the history logs shows that who ever moved the ticket made the change.

I tried to take a screen recording, but low and behold, it stopped doing it for me, however the dev team are still having the same issue as one of them just messaged me saying that it happened again.