Change default assignee for new created issues

[Silvia Saric]

Hello everyone,

Our Project seems to auto-assign all new created issues to a previous co-worker and then another automation auto-assigns it to me. It would like it to assign to me right away because it looks confusing the way it is now - even though it works per se. All new created issues should be assigned to me first/by default and moved to the Backlog.

Any ideas where to look? I have searched for it everywhere but without success.

Automation shows this notification for each new ticket:

[Silvia Saric · Accepted solution]

Issue solved!

My colleague did this: "I created a copy of the workflow, removed statuses that are no longer in use and changed a post-script that automatically assigned all new tickets to Manuel".

[Nikola Perisic]

Hello @Silvia Saric 

In your project settings, what has been set to be the default assignee? Since this is being triggered by the automation rule,can you send a screenshot of this rule? Blur out all of the sensitive information,since these answers could be found by the search engines.

[Silvia Saric]

Hello @Nikola Perisic

Thanks for your quick reply. 

Project default assignee:



Automation rule:

[Nikola Perisic]

This is probably because the previous user was the default assignee.

[Silvia Saric]

So, there's no turning back, what was will always be? :) 

[Nikola Perisic]

You can remove this action Transition issue to - by default when issue gets created, unless you specified your statuses to be different, it will get in the Backlog status. So the second action is not needed. As a final result, make the trigger issue created and assignee issue to yourself.

[Silvia Saric]

Hmm, you mean like this?

[Nikola Perisic]

Yes, that way, when every issue gets created you will be assigned to it. Now this depends if you need exactly all issues or some certain issue types only? (For e.g., when task gets created, you will be the assignee)

[Silvia Saric]

That would be correct as I am a form of gatekeeper for everything that passes from the org to development. I will now stand by and see how the notification will look when I get a new ticket from now on. I will paste it here for future references.

[Nikola Perisic]

You can adjust your personal settings for the notifications specifically:

[Silvia Saric]

Thanks, the settings there should fine now :)

[Nikola Perisic]

If you found this answer helpful,please mark the answer as accepted so everyone who is having this issue can find answers more quickly.

[Silvia Saric]

I will as soon as I get my next ticket, I need to check how the notification looks. Please stand by.

[Silvia Saric]

Writing back to confirm that new tickets are still reported as in my initial question. So the most correct answer from the above seems to be: "This is probably because the previous user was the default assignee."

[Nikola Perisic]

Have you made additional changes and made yourself the default assignee from project settings?

[Silvia Saric]

From my screenshot here it seems to be correct: https://community.atlassian.com/t5/Jira-questions/Re-Re-Change-default-assignee-for-new-created-issues/qaq-p/2796713/comment-id/1047021#M1047021

[Nikola Perisic]

Disable the automation rule and test it again.

[Silvia Saric]

I noticed something now that could be a clue. I remember that in the past we had two Kanban boards, one where "Manuel" was the project lead and he manually pushed tickets to "my" board for development (he was the initial creator and Project Lead for both boards). Now I'm wondering if perhaps the workflow is the problem, that tickets are still going according to that. I tried changing "Manuel's" board to myself as Project Lead but that still didn't do the trick.