Tagging Previous Assignee in the Label Section on Ticket During Transition

[Kaladin Stormblessed]

How can I create a custom automation which adds the name of the previous assignee on a ticket under the label section during a transition which changes the assignee? Doing this so its easier to see who has worked on what ticket during a sprint since our workflow has a lot of different people involved during different stages. 

For example lets take the transition from to-do to In-progress. Lets assume its assigned to person A in the to-do status. When A transitions the ticket to In-progress status, it will be assigned to person B and a label should be created with the name of person A. Any suggestions are appreciated!

[Vishal Biyani · Accepted solution]

@Kaladin Stormblessed 

Labels don't take spaces. With that caveat one possible way is below

1. Have below Trigger

2. While using Edit Issue field, add below is the advanced section

{
"fields": {
"labels": [ "{{fieldChange.fromString.replace(" ", "") }}" ]
}
}

Let me know if this works for you

[Akash Singh · Accepted solution]

@Kaladin Stormblessed You can achieve this use case efficiently by using a multi-user picker field instead of labels. A multi-user picker field is better suited for tracking who has worked on a ticket, as it directly associates users with the issue without the risk of mislabeling or formatting inconsistencies.

You can create a custom field with a name like:

• Previous Assignees
• Worked By
• Assignment History

Automation Rule Setup:

Here’s how you can set up an automation rule to track and update this field every time the issue assignee changes:

1. Trigger:

   • Use the Field value changed trigger and set it to monitor the Assignee field on value added change type as shown below.
     

2. Condition (Optional):

   • Add a condition to ensure the rule applies only during transitions you care about, e.g., the transition to "In Progress."

3. Action - Edit Issue:

   • In the Edit Issue(Advanced) action, update the custom multi-user picker field. You’ll need the ID of your custom field to replace it in the JSON below. Here’s an article that explains how to find your custom field ID: Find My Custom Field ID in Jira.

     Here’s an example JSON for the Edit Issue action (Advanced Edit):

{
 "update": {
  "customfield_xxxxx": [
   {
    "add": {
     "accountId": "{{issue.assignee.accountId}}"
     }
    }
   ]
 }
}

[Kaladin Stormblessed]

Thanks, I have done as you suggested. But the automation never updates the multi-user picker field on the ticket. When I run the automation this is the error visible in the audit log.

[Kaladin Stormblessed]

@Akash Singh I fixed it, I had to remove the field input, and under the advanced section, instead of add, its set. "Add" isnt supported. Check below

---

{
 "update": {
  "customfield_xxxxx": [
   {
    "set": {
     "accountId": "{{issue.assignee.accountId}}"
     }
    }
   ]
 }
}