Jira Automation: Assign an issue to a value looping in a branch

Boyan Iliev_7n6lmk

Hi all,

 

I'm trying to assign newly created bugs, to the guy who worked on the feature. To do so, whenever a link between bug and feature is established, I check the feature assignee and try to apply it on the bug.

 

A feature might have passed several departments - dev, design, localization, etc. So I have a hidden custom field that picks up every single assignee. When the bug gets linked, I get its component and compare it to the groups each assignee is part of. If they match - I got my department and exact person who needs to be assigned.

Example:

1. Bug component is "design"
2. My assignees are "John, Tom, Jack":
   • John is in DEV team
   • Top is in ProductOwner team
   • Jack - in Design team
3. I loop trough the assignees and compare if their ID appears in any of the groups members.
4. Jack gets a match and I have his ID.
5. How to assign this ID to the bug?

 

The issue is when I do advanced branching:

• Smart value: {{issue.customfield_11747}} - my multiple assignee field
• Value: loopAssignees

I manage to find the correct assignee, but I'm unable to assign him the bug. {{loopAssignees}} returns the user ID, but JIRA does not recognize it:

• If I use "Assign work item" both with "Specific User"=>{{loopAssignees}} or "Smart Value"=> {{loopAssignees}}, I get "Issue was already assigned to current user", which is not the case as the bug is "Unassigned"
• If I use "Edit work item" and JSON like the one below, I get "Issues edited successfully", but assignee is not changed
• Both work If I pick a random item from the list, without branching - {{issue.customfield_11747.get(1)}}. I believe its the branching that causes my assignees to loose their "type".

{
  "fields": {
    "assignee": {
      "id": "{{loopAssignees}}"
    }
  }
}

 

Any suggestions on how to achieve this? Both on the overall logic, or specifically on how to get JIRA to understand that {{loopAssignees}} is a user ID?

 

Thank you!

Bill Sheboy

Hi @Boyan Iliev 

Would you please show images of your entire rule (in one continuous image) and the audit log details for the entire rule's execution?  Those may provide better context for this scenario.

Until we see those...

 

I recommend using the Assign User action with the accountId as a variable / smart value for this scenario rather than the edit.

And, I hypothesize you are either hardcoding the "team" list as Created Variables, or populating those team list variables by calling the REST API endpoints and checking groups.

If there is a variable with the list named {{feTeam}} and your {{issue.customfield_11747}} is a multiple-selection user field, you could find the overlapping values using methods described in this article I wrote to use the match() function with regular expressions rather than using the Advanced Branch:

https://community.atlassian.com/forums/Automation-articles/Automation-concepts-Find-Overlaps-Between-Lists/ba-p/3045704

 

And...please remember to add handling to check when no overlaps (i.e., matching user in the team) is found.

 

Kind regards,
Bill