It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can I change default assignee user?

Dzianis Azarenka Jun 03, 2012

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?

18 answers

1 accepted

16 votes
Answer accepted
Thomas Schlegel Community Leader 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


Florian Leray Nov 26, 2015

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...

Like Guang Yang likes this
Richard Hanby May 09, 2018

It's not obvious but as Florian says, Add a Post-function to the transition.

There are some set assignees you can use, or use a custom user by selecting the "Update Issue Field" option

Select Issue Field: "Assignee"

Select the user you wish to assign issue to on creation.

Like # people like this
17 votes
Ronald Vallenduuk Jun 23, 2013

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...

Allan Stokes Jul 26, 2015

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.

14 votes
Michael Rodriguez Oct 09, 2013

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

9 votes
Brian Begy Mar 17, 2014

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

9 votes
Philip Culver Aug 25, 2015

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. 

8 votes
Rilwan Ahmed Aug 18, 2016

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

8 votes
Chris G Feb 12, 2018 • edited

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????

Adrien Terrenoire Feb 22, 2018

Chris, see the javascript submitted by Ihor.   

Navigate to the project's field configuration and pasting the script into the description of the field.  

Chris G Feb 23, 2018 • edited

I guess I'm missing something--how does that javascript help solve the issue? It looks like it just clicks the "assign to me" link/button. That's not helpful and doesn't solve the issue. If I have a project where the "customer" can create issues, but not have issues assigned to them, and I want a default assignee other than the project owner/manager (say I want to push all new tickets to a triage developer) then I fail to see how this helps in any way. New tickets would either still have to be assigned to the project owner or go into a state of unassigned and be automatically assigned to whomever views them first (which is not helpful).

Are you saying that there is a way to use javascript at ticket creation time to assign the ticket to a specific named user? And how would this help for tickets that are created from emails?

It still seems, to me, like a deficiency that has persisted for 5.5 years that could be easily fixed and would create a lot of flexibility for customers.

Adrien Terrenoire Feb 23, 2018

Sorry mate,  I didn't fully internalize your requirement.   You are 100% correct.

Chris G Feb 27, 2018

I was hoping I was missing something...frustrating as it seems such a simple thing for them to fix. However, that's nice you can add javascript to the field description! I didn't know that. That can be handy for some other things.


Michael Jenkins Mar 28, 2018

This is very frustrating. As stated elsewhere, there is a person on my project who is responsible to triage issues. Why can't all new issues be auto assigned to this person? Or even allow me to define a roll called "Default Assignee" and then just put one person in the role.....

Nic Brough [Adaptavist] Community Leader Mar 28, 2018

Make them project lead (you don't have to give project lead any admin), then tell it to assign to project lead.

Or make them a component lead on all components and make component mandatory so the user must fill in at least one.

As mentioned above, whack in a post-function on issue-create that assigns it to that person.

Personally, I agree, there should be another option, maybe "project nominee" handled the same way as "project lead" (but clearly separate). 

I'd also want to add functionality to catch either project lead or nominee being deleted or made inactive - the instant that happens, I'd want to flip both to someone who can take responsibility for the project and triage, although the exact rules there could be complicated (Last active Jira admin?  Last person on the project with assign rights to update any issue in it? etc)

Alex Samad YB Jan 29, 2019

6.5 years .. sigh - i guess they have made their money...

6 votes

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!

Larry LeBron Oct 06, 2015

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.

Anna Baumgard Dec 16, 2015

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

5 votes
Walter Nissen Jun 24, 2013

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.

5 votes
Hyme Schachter Aug 25, 2015

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

4 votes
Ron Waldon Feb 23, 2014

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.

Dávid Balakirev May 06, 2015

This is works with JIRA v6.1.4.

4 votes Mar 01, 2016

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?

Florian Leray Mar 01, 2016

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

Florian Leray Mar 01, 2016

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

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.

Like Benjamin Bartels likes this
4 votes
Ihor Tretyakov Oct 03, 2017

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();};
Adrien Terrenoire Feb 22, 2018

Thanks Ihor. This is exactly what I needed (and I learned that js can be used in the field descriptions)!

Val Perry May 02, 2018

I'm new to Jira, and not sure how to find Issues Configuration. Could you please list the steps how to navigate to the field where to add that script, using new Jira GUI?

Amir Katz May 31, 2018

It's a nice hack, but IMO, putting executable code in a text field is really a bad idea, reminds me of SQL injection :-(.

3 votes
Yves Jaques Oct 22, 2013

Agreed, Ronald's situation mirrors my own.

2 votes
Yotam Shtossel Sep 18, 2018

This bug / "feature" / behavior is embarrassing.


6 years in the making and no traction on this trivial - and obviously required by the (paying) community - issue?

Nic Brough [Adaptavist] Community Leader Sep 18, 2018

This is an old thread, and also unclear from what looks like edits and removals.

Rather than try to dig stuff up, could you explain what you think the "bug" is here?

Yotam Shtossel Sep 19, 2018

Hi Nic,


The fact that the thread is old is probably a badge of shame. That's the relevant web search hit that I picked up when trying to find a solution for the issue - and it's spot on.


We also have this scenario in which we want default assigning of a project issues to one person but have another person that is the lead (with all of the privileges). The comments before my own provide the reasoning on why the proposed workarounds are difficult and not always applicable.


In some organizations (mine included), you have some autonomy in your own JIRA projects but you can't change the issue workflows etc.


I'm repeating comments from above - but again - it's amazing that this trivial issue is still open 6 years in. Does not reflect well on JIRA.

Nic Brough [Adaptavist] Community Leader Sep 19, 2018

Mmm.  What "bug"?  I suspect this is old because there is no real bug here, just a handful of people with edge-case requirements around trying to automate stuff because their processes don't make the usage simple enough for their users.

Walter Nissen Sep 19, 2018

Hi Nic,

The current setup makes it difficult to have a person who triages issues. The option to have the project owner be the triager is helpful, but if you want to have a QA lead or similar person take on that task, they need to be made the default assignee for all components, or one of the Javascript workarounds needs to be applied. I am surprised it is still being discussed years later, as it seems simple to me.

Nic Brough [Adaptavist] Community Leader Sep 20, 2018

Set them as the project lead.  If you're doing triage through a single person, then you don't need the component stuff at all, or any javascript.  As they're the one assigning the work, they're the project lead (and you can just mention the project owner in the project description, if that's a different person)

Sarah Bailey Dec 11, 2018

"Edge-case"? Wow.

Joydip Chakravarty I'm New Here Jan 11, 2019 • edited

I agree with Sarah. If the number of separate people commenting on this and similar threads is any indication, MANY users (myself included) are in the same boat.

2 votes
Christopher Brown Oct 15, 2018

I love the arrogance here from people who represent Atlassian on these forums.  "Edge cases" my arse.

I have seen this with quite a few features that are missing in Jira and should be core.

Standard responses:

  1. There is a plugin that does this (usually not very well)
  2. It is an edge case (although lots of people seem to have them)
  3. Here is some Jira Query code that can do it
  4. Here is a workaround
  5. It is not a bug

It smacks of the Microsoft way and gives me a very bad vibe about the software ongoing.  As a customer it is making me wary of integrating our processes too much further with Jira.

Amir Katz Oct 15, 2018

@Christopher Brown I share your pain...regarding point #1, even if the add-on does the job right, it usually costs $$$, which may be sometimes 25% of what you are paying for the core Jira.

BTW, Nick Brough, who called this an "edge case", is not from Atlassian, but from Adaptavist, who make the excellent ScriptRunner add-on.

But when I look at all different functionalities that ScriptRunner provides, many of them should have been core features (e.g. load options to a selection field from a text file instead of typing them manually, one by one, in the UI).

Just my $0.02 

Joydip Chakravarty I'm New Here Jan 11, 2019 • edited

Interesting... so by defining these requests as "edge cases", he's advocating that they don't get added to Jira, so his company can continue to provide value filling in the gaps (that, in some cases, Jira shouldn't have).

That being said, I do appreciate Adaptavist providing an option that Jira is not. And also for @Nic Brough [Adaptavist] being on the forum and providing help and guidance to other members.

0 votes
Tos Crawford Apr 28, 2016

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.

0 votes
Zubin Thomas Sep 14, 2018

This issue is not yet fixed. When I move an issue from "To do" to "In Progress", the assignee gets changes to the person who is moving the issue.

How to fix this?

Nic Brough [Adaptavist] Community Leader Sep 16, 2018

Remove the post functions, automation or listener that is doing it.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Jira Software

Early Access: If you use Jenkins and Jira Software Cloud, you need to read this!

The Jira Software Cloud Team has been busy working on a simple, secure, and reliable way to integrate your build and deployment information from Jenkins with Jira Software Cloud. This means you don’t...

271 views 0 8
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you