Change Assignee based on a custom field

So I understand that JIRA doesn't have this capability built in.

We want a post function in the workflow to automatically assign a user based on a specific custom field. For example, we have a field called "Unit Tester" where we choose a person who is going to be the unit tester at the beginning of our workflow. We want to pull that value out at a step later in the workflow, and make that person the assignee.

I was wondering if there are plugins out there that allow you to do that?

And we don't want the Unit tester to be chosen by anyone other than the person in the beginning of the workflow, so just changing the assignee manually late in the workflow won't fly.

5 answers

1 accepted

That's what I needed. Thanks!

Yup, that's what I needed. Thanks!

Is there anyway through which we can copy one of the customfield of parent ticket to asignee of Sub ticket.

Customfiled in parent ticket is user picker field.

Try JJupin if you want abstraction from the Jira internals. Or, you can use Script Runner ...

1) Add a Post Function to the WF transition

2) Click Copy Value From Other Field

3) Give these values:

Source Field = Custom Field

Destination Field = Assignee

This doesn't seem to work. I am able to copy one custom field's value to another(both of type User). The copied value appears on view screen. But when I copy the same custom field's value to assignee, the value is in the db, but not on the view screen. Have any idea what is the problem^

I have the same problem. This doesn't work for the Assignee field. It ends up staying unassigned after completion.

Hi Jessica,

I had the same problem and turned out that the user which makes the change in the background (in our case JMWE user) didnt have permissions to edit issues. This user is automatically assigned to the project role Atlassian-addons-project-access. By giving this role the permission to edit issues, the JMWE user was able to copy the field value to the user.

Hope this helps.

@Annette G.

I never knew what that project role was for. Quick question you state that the JMWE user needs to in the role. Is that explicit? Or is that a facet of JIRA plugins that any needed users are implied? I see the role in our instance but no users assigned to it. I don't see a JMWE user in the system either. Thanks for any more insights you can provide. Thank you so much for replying!

NOTE: appears that just adding the project role (atlassian-addons-project-access) to the projects permission scheme for Editing Issues  must give an implied connection for the JMWE user as I made no other changes and it worked.

you can use the "Set a field as a function of other fields" function in JIRA Workflow tool plugin.



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

3,006 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