How can I change default assignee user?

I'm creating an issue. You will see "automatic" if you look at аssignee field. I want to change automatic user from Jack to John. How can I do?

15 answers

1 accepted

12 votes
Thomas Schlegel Community Champion Jun 03, 2012

Hi Dzianis,

the default assignee is either the project lead or it is "Unassigned".

If you have defined Components for your project, you can specify a "Component Lead" and make him the default assignee for all issues regarding this component.

Have a look here:

Best regards


default assignee can be anyone now : add a post-function "Assign to..." on the "Create" transition through the workflow diagram view, all your issues can be assigned to whoever you like, reporter, lead, project role...

Is this likely to change any time soon? I find this quite limiting.

I'm project lead but I'd like my QA lead to triage new tickets. That means I have to set the QA lead as Component lead for all components. And if the QA lead changes I have 27 components to update...

I'm back to JIRA for the first time since 2009. An hour into setting up an IT project where 90% of the work will be done by a consultant, but for which I'm the lead because he simply doesn't know our environment, and already kaboom! it's my first head-smash-into-glass-desk moment.

Also I think there should be a Default Assignee option of 'Reporter'

Why is this so broken? Unassigned is not a valid state for an issue. Why is this so broken?

See YOUR PROJECT -> Administration -> Roles -> Default Assignee.

You can only set it to the Project Lead (or unassigned). This is so that issues without a Component can be assigned to the Project Lead by default.

This is works with JIRA v6.1.4.

You can add a post function to the create issue transition that will set the assignee to the reporter, the current user or the project/component lead developer.

When editing the workflow select the Diagram view, select the create issue transition. A box will pop-up with a 'Post Functions' link. Go here and the rest is straight forward.

Still not quite as flexible as I'd like but maybe it helps!

If I understand correctly, this still requires a transition in states for it to take effect, correct? We'd like to see the functionality which would make "Reporter" the default at the time of issue creation.

"Create" is a transition between "Create" and "Open".

I would very much like to see the capability to set the Default Assignee to Reporter

Ditto on wanting to change the default assignee. The larger a project is, the less likely the lead will be doing triage, and the more painful to change the default setting on every component.

Agreed, Ronald's situation mirrors my own.

It's pretty crazy that this is still an issue at all. Why is Atlassian digging their heels in on this? The question was asked literally 3.5 years ago. Allowing the default assignment to be any user should not be a difficult change. I'd love to hear from them why they aren't willing to make that change. 

this is really still an issue?

I own projects A, B, and C, but I have different developers assigned to work tickets for those projects.  Why can't I be the project lead, but have the default assignee be those 3 different developers?

You can. Just create a post action on the "Create" transition in the workflow and that's it.

Though you cannot really assign an issue to 3 people at a time in JIRA...

i'm not trying to assign an issue to 3 people.

  • projectA, lead: me, default assignee: developer1
  • projectB, lead: me, default assignee: developer2
  • projectC, lead: me, default assignee: developer3

i'm the lead on all 3 projects, but each has a different developer who should get assigned any tickets that come in.

a tickets should never be unassigned, so they're all getting assigned to me and the workflow is for me to then turn around and assign it to developerX depending on the project.  it's a waste of time.

Atlassian should allow to change "Default Assigne" to any user.

The solution, allowing any user to be assigned as default, must not override if the creator assigned an assignee. 


Wouldn't be such a bad idea to allow different default users by issue type either.

JIRA 7.5

Go to Administration/Issues/Field configurations/Configure

On Assignee field click Edit

Put this code in Description

<script type="text/javascript">
AJS.$(document).ready(function() {
if (AJS.$("#assignee").val() == "-1"){AJS.$("#assign-to-me-trigger").click();};

5.5 years later and this still hasn't been fixed????? What is the reasoning behind not allowing the default assignee in a project to be anyone I want it to be? I use the same workflow for multiple projects, so adding a transition step to set an assignee is a hack that doesn't work (since I'd then have to have separate copies of the workflow for each project where the assignee is different from another project). Instead of forcing me into hacks that don't work why not just fix this????

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,832 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot