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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I used {{changelog.fromString}} it doesnt edits the field in JIRA only removes the Inactive user from Logs
Any idea how to get the previous values only iam working on Multiuser picker field
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have created this for you to show how you would do it. Obviously, if you have a Multiuser picker field just replace it with the assigned in all instances.
Here are the smart values so you can copy/paste :)
{{#changelog.[field name]}}{{fromString}}{{/}}
{{#changelog.[field name]}}{{toString}}{{/}}
I hope that helps!
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.
HI,
I was able to resolve the issue that field was also there in other automation to be edited i just changed the triggers and it worked
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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? :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.