Auto-assign based on value selected in the custom field ONLY IF assignee field is left unassigned

John_Diaz

I have a working script below on my custom field called Target System with two values JIRA and Confluence and will assign to the desired user based on what you select once you create the ticket.  However, I want to set another conditional that should the reporter know who to assign the issue to then it won't auto assigns.

Example 1: I select JIRA under the Target System field and assign to John Doe, then it will leave the assignee to John Doe.

Example 2: I select JIRA under the Target System field and leave assignee automatic then will automatically assign to JIRA TEAM. 

My post function script below:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.ComponentManager
import com.atlassian.jira.issue.CustomFieldManager
import com.atlassian.jira.issue.customfields.manager.OptionsManager
import com.atlassian.jira.issue.fields.CustomField
import com.atlassian.jira.event.type.EventDispatchOption

String userName;
def customFieldManager = ComponentAccessor.getCustomFieldManager()
def cf = customFieldManager.getCustomFieldObjectByName("Target System")
def cfTargetSystem = issue.getCustomFieldValue(cf)
switch(cfTargetSystem){
case "JIRA": userName = "JIRA Team";break;
case "Confluence)": userName = "Confluence Team";break;

}
log.error(userName)
log.error(cfTargetSystem);
def user = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()
issue.setAssignee(ComponentAccessor.getUserManager().getUser(userName))
ComponentAccessor.getIssueManager().updateIssue(user, issue, EventDispatchOption.ISSUE_UPDATED, false)

PD Sheehan

First, I would be remiss not to mention that Components already provide this exact feature. If you create JIRA and Confluence as components in your project and set the component leads accordingly, the assignee will be set in this order 1) user-selected assignee, 2) Component Lead, 3) Project Lead

Assuming, you have a valid reason not to use components, let's proceed ...

None of my environments are set up to allow unassigned issues, so I can't test for sure, but wouldn't it be as simple as wrapping the whole script into an if(issue.assignee){  } block?

I would assume that an "unassigned" issue would have a null value for assignee field.

Also, I should point out that for most cases, post function don't need to run updateIssue if you use IssueInputParameters. This way you don't duplicate db transaction and will reduce the performance impact of your postfunction. Something like this:

import com.atlassian.jira.component.ComponentAccessor

if(issue.assignee){
   String userName;
   def customFieldManager = ComponentAccessor.getCustomFieldManager()
   def cf = customFieldManager.getCustomFieldObjectByName("Target System")
   def cfTargetSystem = issue.getCustomFieldValue(cf)
   switch(cfTargetSystem){
      case "JIRA": userName = "JIRA Team";break;
      case "Confluence)": userName = "Confluence Team";break;
   }
   log.error(userName)
   log.error(cfTargetSystem);
   def assignee = ComponentAccessor.getUserManager().getUser(userName)
   issueInputParameters.setAssigneeId(assignee.id.toString())
}

I removed unused imports.

This function would need to be BEFORE the built-in function that stores the issue to the db.

In groovy, you can do without the switch construct. I'm a big fan of something like this:

import com.atlassian.jira.component.ComponentAccessor

def systemUserMap = [
   JIRA: 'Jira Team',
   Confluence: 'Confluence Team'
]
if(issue.assignee){
   String userName;
   def customFieldManager = ComponentAccessor.getCustomFieldManager()
   def cf = customFieldManager.getCustomFieldObjectByName("Target System")
   def cfTargetSystem = issue.getCustomFieldValue(cf)
   userName = systemUserMap[cfTargetSystem]
   log.error(userName)
   log.error(cfTargetSystem);
   def assignee = ComponentAccessor.getUserManager().getUser(userName)
   issueInputParameters.setAssigneeId(assignee.id.toString())
}