nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Muhammad Khan_hom3hu

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.

Accepted answers

John Funk

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.

All comments

John Funk

Hi Muhammad - Welcome to the Atlassian Community!

Muhammad Khan_hom3hu

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_hom3hu

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:

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud