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!
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!
Everything below is tested on Ubuntu 17.10. I prefer to use Jira in a docker container because: 1. I can install Jira with a couple of commands. 2. I can start and stop Jira just by starting and s...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot