Set Assignee in Post Function

Pushparaj Bhaskaran June 3, 2013
On Create Issue transition need to set the assignee to a different user using Groovy Script . I have Script runner plugin installed. The following is the script which import com.atlassian.jira.ComponentManager import com.atlassian.jira.issue.CustomFieldManager import com.atlassian.jira.issue.Issue import com.atlassian.jira.issue.MutableIssue import com.atlassian.jira.issue.comments.CommentManager import com.atlassian.jira.issue.fields.CustomField import com.atlassian.jira.util.ImportUtils import com.atlassian.jira.user.util.DefaultUserManager import com.atlassian.crowd.embedded.api.User MutableIssue issue = issue UserManager userManager = UserManager.getInstance(); User usera = userManager.getUser('my_user_name'); issue.setAssignee(usera); It provides me with the below error on execution Script15.groovy: 13: unable to resolve class UserManager @ line 13, column 13. UserManager userManager = UserManager.getInstance(); ^

5 answers

1 accepted

1 vote
Answer accepted
Vidic Florjan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 3, 2013

You can try:

import com.atlassian.jira.ComponentManager
import com.atlassian.jira.issue.CustomFieldManager
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.issue.comments.CommentManager
import com.atlassian.jira.issue.fields.CustomField
import com.atlassian.jira.util.ImportUtils
import com.atlassian.jira.user.util.UserManager
import com.atlassian.crowd.embedded.api.User
// added line no.1
import com.atlassian.jira.component.ComponentAccessor

// added line no.2
userManager = (UserManager)  ComponentAccessor.getUserManager()
MutableIssue issue = issue
  
User usera = userManager.getUser('my_user_name');
   
issue.setAssignee(usera);

Pushparaj Bhaskaran June 23, 2013
Yes , it works Also need to add issue.store()
1 vote
Christian Czaia _Decadis AG_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 3, 2013

Posting code formatted as code in a readable way (CR/LF...) will increase your chances of getting help...

0 votes
František Špaček _MoroSystems_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 11, 2020

Correct way as of 2020 is using

issue.setAssignee(user)
issueMgr.updateIssue(currUser, issue, EventDispatchOption.DO_NOT_DISPATCH, false)

 issue.store should not be used in scripts at all, according to message it shows when you put in console:

obrazek.png

 

Whole script:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.IssueManager
import com.atlassian.jira.user.ApplicationUser
import com.atlassian.jira.event.type.EventDispatchOption

UserManager userMgr = ComponentAccessor.getUserManager()
IssueManager issueMgr = ComponentAccessor.getIssueManager()
ApplicationUser currUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()

ApplicationUser newAssignee = userMgr.getUserByName("username")

issue.setAssignee(newAssignee)
issueMgr.updateIssue(currUser, issue, EventDispatchOption.DO_NOT_DISPATCH, false)
0 votes
Sascha Ziemann January 7, 2020

API seems to have changed. Nothing on the page worked for me. But this works:

issue.setAssignee(ComponentAccessor.userManager.getUser("someuser"))
issue.store()
0 votes
Zul NS _Atlassian_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 3, 2013

According to previous discussion on this in here. Mizan suggested to try use the following instead

ComponentManager.getInstance().getUserUtil().getUser('ngs')

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events