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
When I create an Epic and then it creates an issue, all of the tasks get assigned to me even though when I created it in the Automation, I put Unassigned for the Assignee.
It would be better to figure out how it is getting assigned to you in the first place and remove that.
There is either a post function in the Create transition for the workflow, or maybe the project is setup to assign tasks to you as the Project Lead or Component lead. I would check there first.
Also, check the history of the tasks that are getting created. It might be that the task is getting created with Unassigned, but then something else is running to then assign it to you. If that is happening, it will show up in the history.
First, let's check the history to see if it says who is updating it. Have you done that? Do you know where that is?
Did you look at the history, and is there a separate entry that updates the assignee after the issue is created? Can you share a screenshot of the history?
Thanks - that's very helpful. That tells us that there is not another automation that is doing it.
So, let's look at the project settings.
Go to Project Settings on the bottom left while on the project. The click on the Details page. Is there a Default Assignee?
Yes, that will hopefully fix it. Give it a try and see. Then you should also take out the action that is setting the issue to Unassigned in your automation - it would just be adding overhead to the rule.