Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,672
Community Members
 
Community Events
184
Community Groups

Unable to automatically assign via automation

Krishna Chaitanya
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Mar 21, 2023

I am trying to restrict wrong assignment of tickets to users by creating an automation that resets the field of assignee if anyone outside of my group of users tries to change the value. I have achieved this by using this to set user upon the automation trigger:

{{fieldChange.fromString}}

I have attached a screenshot of the error I am getting when trying to do this. It just says Inactive user even though this is an active user of my project and space. Can someone help me with what i need to do differently to avoid this from happening? Screenshot 2023-03-21 at 3.10.46 PM.png

2 answers

I am having the same issue! I have been trying to resolve it but no dice. I 

@Krishna Chaitanya @Randy Michel 
Options are:
1. Try using {{changelog.fromString}} instead of {{fieldChange.fromString}}
2. Set up a backup custom field (Back-up assignee) that stores the assignee by automation every time is set by your group of users. Then create another automation with the "assignee" as a trigger and the condition is that if the initiator of this event IS NOT a member of your group then edit the assignee and copy the value from the "Back-up assignee" field.

Hi @Krishna Chaitanya

Is there any particular reason why you chose not to restrict assignee changes in the project permission scheme to that specific group of people? :)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events