Script Runner Create subtask set assignee in additional code

Hi everyone,

I'm using the standard script workflow functions to create a subtask. I want to set an assignee for the subtask. I have used both suggestions here https://answers.atlassian.com/questions/260649/create-subtask-with-scriptrunner-setting-assignee(issue.assigneeId = "username") and here https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-Fast-tracktransitionanissue(issue.setAssigneeId('spodyacheva')) for setting the assignee in this field, but neither of them seems to be working.

We had previously implemented the setAssigneeId action, which had worked, but it seems to have broken after an upgrade from 5.1 to 6.2. I didn't read anything about anything like this changing in the release notes, but could I have missed someting? Do I need to go back and change all these post-functions? What do I need to change them to?

Thanks in advance for the help!

3 answers

1 accepted

Hi,

use the following in additional actions

issue.assigneeId = "username"

Hope that helps

Thanks for the suggestion. Unfortunately, that doesn't work either. :(

If I add that to the additional actions section, the issue is created as unassigned.

What's your JIRA and plugin version?

I use the JIRA 6.2.0 and scriptrunner 2.1.17 and works fine.

I wish it were something like having an old version. Commented, Jamie, on your post above just a moment ago. My apologies again for wasting everyone's time. In any case, thanks for providing the most recent code.

Yeah, me too. I suspect the OP has an old version of something.

No problem. Thanks for fessing up!

issue.setAssigneeId("username") worked for me.

0 vote

Is this 6.2(.0), and which version of script runner?

I'm embarrassed to admit it, but it's my mistake on this one. The wrong workflow was assigned, and this workflow had an "assign issue" postfunction on issue creation. Sure enough, works like a charm now that the correct workflow is assigned. There must have been some sort of interactions going on there that caused the issue to come up as unassigned in the end. Thanks for your time, and sorry to be a bother!

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,314 views 14 20
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