1 answer
1 accepted
After testing today around 4AM-4PM UTC timeframe, I don't think this worked unfortunately :(
So here's how I directly plugged your snippet into the lastIssueWithAssignee block:
// Find the latest created issue id that has an assignee
def lastIssueIdWithAssignee = issueManager.getIssueIdsForProject(issue.projectObject.id)
.sort()
.reverse()
.find {
def foundIssue = issueManager.getIssueObject(it)
def jql = /project = $issue.projectObject.id and "Original Assignee" is not empty and assignee is not empty and issueType=Defect and Created > -30d order by Created desc/
def parseResult = searchService.parseQuery(foundIssue.assignee, jql)
def lastAssigned
if (parseResult.isValid()) {
def results = searchService.search(foundIssue.assignee, parseResult.query, PagerFilter.unlimitedFilter)
log.info results.total
lastAssigned = results.results.find {
def hour = it.created.toInstant().atZone(ZoneOffset.UTC).hour
hour >= 4 && hour < 16
}?.assignee
}
return lastAssigned
This is the list of users in the 'Operations' role that are to be assigned in round robin between 4AM-4PM UTC (in order):
1) Ary D
2) Chen S
3) David Y
4) Dominik M
5) Fernando B
6) Gamal D
7) Rasanga S
The last issue that was assigned to someone in that timeframe from the previous day was 'David Y'.
Now today, entering the 4AM-4PM UTC timeframe again, I created another issue and expected that it would auto-assign to 'Dominik M', picking right back up where it left off from the other day. It instead defaulted to the first user in the list of 'Operations' users ('Ary D').
-----
Also I tried running the snippet through console, but doesn't seem to work, stating that lastAssignee has to be declared:
Sure thing, here are the screenshots:
And regarding your observation, originally yes. The plan was to assign to the same user twice in some instances through the round robin cycle before moving on to the next one.
But then I figured just widen the scope of users to cycle through..basically instead of assigning tickets to users twice in a row, just include a different user to take that second ticket, just to make life easier.
So instead of:
def users = ["user1","user2","user2","user3","user4","user5", "user6","user7","user8","user9","user10"]
I just added another user to the array:
def userNames = ["user1","user2","user2","user3","user4","user5", "user6","user7","user8","user9","user10", "user11"]
In the end, I want to be able to assign the users in the array above in round-robin order, similarly to Adaptavist's Round Robin example, yet not based on users in a project role, but rather users manually listed in an array within the script.
No, I meant a screenshot like this one:
The problem with your user array approach is that this line:
def lastAssigneeIndex = userNames.indexOf(lastAssignee)
When the lastAssignee is "user2", will always return index=1.
So round robin witll start with user1, next time, it will find user1 (index=0) and move to the next user in the array (user2). The next itteration, i will find user2 (index=1) => next user = user2. The 3rd itteration, it will find user2 (index=1) again and the next it the list will be user2 again. The 4th and all subsequent itteration will always repeat the same last assignee = user2 (index=1) next assignee= user2.
That what I mean by needing to either looking at the last 2 assignees or keep track of the last assignee index separately.
For example, create a new custom field call "Round Robin Assignee Index" and update your issues each time you assign them to the index corresponding to the new assignee. Then when you get the lastIssueInTimeRange, lookup the "Round Robin Assignee Indx" instead of assignee, then use that to find the next assignee.
An alternative would be to store a custom application property:
//store a custom property
ComponentAccessor.applicationProperties.setString('customRoundRobinIndex', lastAssingeeIndex)
//retrieve a custom property
def lastAssigneeIndex = ComponentAccessor.applicationProperties.getString('customRoundRobinIndex')
With this, you don't even need to bother with searching by JQL ... just keep track of that number and each time you assign to a new person, you increase the index (or set it to zero if you've reached the max).
Here is a much-simplified version:
import com.atlassian.jira.component.ComponentAccessor
import java.time.ZoneOffset
def customFieldManager = ComponentAccessor.customFieldManager
final originalAssigneeCustomFieldId = "customfield_20321"
def originalAssigneeCustomField = customFieldManager.getCustomFieldObject(originalAssigneeCustomFieldId)
// If it is true, the assigned issues will be reassigned
final reassignIssues = false
if (issue.assignee && !reassignIssues ){
//issue is already assigned, and we don't want to re-assign
return
}
def createdUtcHour = issue.created.toInstant().atOffset( ZoneOffset.ofTotalSeconds(0)).hour
if (createdUtcHour <= 4 && createdUtcHour >= 16) {
//issue was not created in the in target time range, nothing to do
return
}
def userNames = ["userkey1","userkey2","userkey3","userkey4","userkey5", "userkey6","userkey7","userkey8","userkey9","userkey10", "userkey11"]
def lastAssigneeIndex = (ComponentAccessor.applicationProperties.getString('customRoundRobinIndex') ?: 0 ) as Integer
def nextAssigneeIndex = (lastAssigneeIndex + 1) % userNames.size()
ComponentAccessor.applicationProperties.setString('customRoundRobinIndex', nextAssigneeIndex.toString())
def nextAssignee = userNames[nextAssigneeIndex]
def nextAssigneeUser = ComponentAccessor.userManager.getUserByName(nextAssignee)
issue.setCustomFieldValue(originalAssigneeCustomField, nextAssignee)
issue.setAssignee(nextAssigneeUser)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.