Auto-assign issue to user selected in a custom fields on status change trigger

[Muhammad Khan]

Hi,

So I manage several projects that have the following structure.

Issues have custom fields:

1. Assigned Dev

2. Assigned QA

3. Assigned Reviewer

4. Assigned Dev Ops

And statuses are:

1. In Development

2. In Testing (BETA)

3. In Review

4. Verified (Pending Deployment)

5. In Testing (LIVE)

6. Done

I want to add automation to change the assignee of the issue based on it's status.

I want to do it like this:

When status -> "In Development", change the assignee to Assigned Dev

When status -> "In Testing (BETA)" or status -> "In Testing (LIVE)", change the assignee to Assigned QA

When status -> "In Review", change the assignee to Assigned Reviewer

When status -> "Verified (Pending Deployment)" change the assignee to Assigned Dev ops

Is this doable without adding a custom script?

I am open to any and all solutions. If custom script is the only solution, I would appreciate it if someone can point me towards a good tutorial/documentation on JIRA custom scripts.

[John Funk · Accepted solution]

Hi Muhammad - Welcome to the Atlassian Community!

Yes, you can achieve this with Automation Rules. Create a rule based on a trigger for Issue Transitioned. Select the Status it is transitioning to and then add a new action for Edit Issue. Select the Assignee field and then copy the value from the appropriate custom field. 

[Muhammad Khan]

Hi John, Thanks for your answer.

Yes, I am aware of that. I tried it as well.

But the custom fields do not appear in the dropdown of values to copy from.

One option I saw was to add the action "Assign Issue" Instead, I did that and used the smart value of "{{customfield_Assigned Dev}}" but that automation rule just sets the assignee to "Unassigned".

[John Funk]

Can you share a screen shot of the rule as you have it now? That syntax that you have is not correct for the field name. 

Are the custom fields all single user picker fields? They should show up to copy from. 

[Muhammad Khan]

Yes, the custom fields are all single-user picker fields.

Here are the screenshots of the current rule:

Here the custom fields are not appearing in dropdown:

[John Funk]

Use Edit Issue instead of Assign Issue. Choose Assignee and then see if you can copy the value from the Custom Field.

[Muhammad Khan]

Hi John, I am very late in replying to this.

But I tried this out as well, I specified the Smart value using "Edit Issue" instead but it doesn't copy over the value, the automation runs successfully but it doesn't change the value.

[Michael Corona]

Did you ever get an answer for this Muhammad? I am trying to do a very similar operation.

[Muhammad Khan]

No @Michael Corona , I never did manage to find a way to get this done.

The issue is in identifying the id of the custom field. I believe if the ID is correctly identified then the answer by @John Funk to use Edit issue instead of Assign Issue would work.

If you do find a way, please let me know as well.

[Michael Corona]

@Muhammad Khan  @John Funk I figured it out today.

You need to extract the accountId of the custom field in the automation rule. Essentially what you said, but there isn't a good way to extract that information until I used the Jira cloud plugin for excel. Some of the meta data for each custom field was shown that I started trying in the automation rule. 

This is all using the smart value type in the then trigger.

 

So now my automation rule looks like this:

When I transition status, it now successfully populates the assignee with whoever is in that custom field.

[Muhammad Khan]

@Michael CoronaThanks a lot. This worked for me too.

I found my custom field IDs by Inspecting the custom field using Browser Dev tools.