You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am trying to make some automations for our Jira and I wanted to create one when a sub-task got moved from "To Do" to "In Progress", the parent task would do the same.
The transition automation works perfectly fine, but Jira automatically deletes the current assignee and changes it to "Automation for Jira", no matter what setting I choose.
Am I doing something wrong here? I merely want the current assignee to still be the same assignee after the automation is triggered.
Hello @Jesper Kjær
Welcome to the Atlassian Community!
Per your description, I understand that you want to configure an automation rule to keep the status of the parent issues synced with their sub-tasks when any related sub-task get transitioned to "In progress", however, keeping the assignee field untouched. Is that correct?
I believe there are two steps in your automation rule that might be misconfigured:
1 - The condition "And: Some sub-tasks match" is not necessary in this case, since the rule will be triggered every time any sub-tasks are transitioned to In progress. That being said, this condition will never fail because of the trigger, so you can remove it and the rule will still work as intended.
2 - I believe the action "And: Assign the issue to" is the one causing the assignee of your issues to be changed to the "Automation for Jira" user. As you can see in your rule details, the Automation for Jira user is the default actor of your automation rules, so that's the user triggering the event.
In fact, I'm not sure what you are trying to achieve with that action, so:
Let us know if this information helps.
Hello @Jesper Kjær
If the issue is not fixed after the steps provided, I can confirm to you that the root cause of the problem is not related to this rule. That being said, it leaves us with the following possibilities:
1 - You have another automation rule that is causing the issue. I suggest you to check if there are other rules that would change the assignee field and that can be triggered by the mentioned rule.
2 - You have a workflow post-function that is automatically updating the issue assignee when it gets transitioned. I suggest you the following steps to troubleshoot it:
If the steps above did not work for you, please provide us a screenshot of your current automation rule and another one from the post functions you have in your "In progress" transition.