Why subtasks are automatically unassigned when completed?

[Paul Catarig]

Hi all,

On the project I'm currently working on, each time after a subtask is done, the subtask is automatically unassigned. 

We are using a Scrum board with 3 lanes: To do, In progress and Done. In a few words, the process is like this: task is in To do state -> Task assigned to dev -> task In progress -> task done.

What can I do in order for it to remain assigned also when it is in the Done state (not assign it again manually, of course)? 

Does anyone know where the problem is?

Thank you,

Paul

[Tarun Sapra]

Hello @Paul Catarig

If the sub-task had a assignee before being done and then after getting done the assignee is removed then this is happening due to an workflow post-function.

Can you share an screenshot of the workflow postfunction for the transition to Done.

[Paul Catarig]

Hi @Tarun Sapra,

Thanks for your reply.

When I was trying to reach the workflow transition, in order to take a screenshot, I saw that I have to contact the admin in order to be able to view/edit something.

That means, I assume, it is something set internally by our organization.

I will try to reach the admin.

Thanks and regards,

Paul

[Deleted user]

Hi. 

To me it sounds like there is a condition applied to the workflow.

Regards, 

Martin. 

[Deleted user]

It could also be a post function that unassigns the user from the sub-task. 

[Nic Brough -Adaptavist-]

Not a condition.  A condition is used to control access to a transition.  It is possible to write a condition that would update an issue, but it would be hard work and spectacularly dumb, as the code would run every time someone looked at an issue.

You really mean "post function"

[Deleted user]

Excuse I was writing the post while driving :)
Hence I corrected (while driving) that it is a post function.