Automation to trigger when someone tries move a task or subtask

[Claire Hendrick]

I had a problem recently where someone moved a sub-task I assigned to them on my teams board to their own team board. This caused a lot of unnecessary back and forward trying to find the new task, figure out who it had been assigned to and what stage it was at. To prevent this happening again I am looking a a way to trigger a flow that clones and links the tasks instead of just moving it

Current manual Flow:

A Task is created on board A

A subtask is created and assigned

The assignee moves the subtask to their own board, board B

The subtask is no longer related to the orignal Task and is hard to track

Automation Idea:

Manual - A Task is created on board A

Manual - A subtask is created and assigned

Automation Trigger - The assignee tries to move the subtask to their own board, board B

Automation - instead of moving the task, the task is cloned to board B

Automation - orignal task still exists and is linked to the cloned task

[Trudy Claspill · Accepted solution]

Hello @Claire Hendrick 

Welcome to the Atlassian community.

Boards display issues based on filters. Is the other team's board filter referencing a different project/issue-set than the original board?

When you say the user "moved" the sub-task, do you mean they used the Move functionality to change it from being the child of a Task in your project to being a child of a Task in their own project? Did they move the issue to a different project than it was in originally?

You cannot create an Automation Rule that prevents the moving of an issue. Automation rules are triggered by completed events. You could only create a rule that recognizes that an issue has been moved, and then take actions as a result of that.

Have you considered taking away the Move Issue permissions for Team B in Team A's project? That should prevent them from moving the issue.

You could create a Manual automation rule that Team B would use to create a copy of the sub-task into their own project, and in that rule you could also create a link between the two sub-tasks.

[Claire Hendrick]

Hi @Trudy Claspill 

I suspected that would be the case. I had tried many different options as to me the Trigger Issue would be the orignal issue, not the one created after the move.

I was hoping that I was just missing something along the way, but thanks for clarifying. I agree, the way to go is to remove the permission to move issues.