You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
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.
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".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Use Edit Issue instead of Assign Issue. Choose Assignee and then see if you can copy the value from the Custom Field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.