Hi
I tried to create an automation rule for the priority field of the ticket.
Only admin can change priority, but it not actually work.
What I am doing wrong?
Trigger:
When: Value changes for
priority
Condition:
Initiator is not in
Action:
Then: Transition the issue to
same status (loop)
Hi @Aleksey Plisko and welcome to the community,
what are you actually trying to do with the transition action in the end? The transition will only change the status but won´t touch the priority field.
As far as I got your requirement right you´d like to rollback the priority field in case somebody NOT in admin group changed the field. Could you confirm this?
If so I would suggest to work with fieldChange smart value. {{fieldChange.fromString}} will give you the value of the field before the change. If condition is true the value can be set back using this smart value. see detailed documentation here:
https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--eventType--
Hope this was helpful.
Best
Stefan
Yeah, you got it right.
Could you provide me please an example of how to use it?
And where do I actually enter these smart values/commands?
Thank you in advance
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
instead of an transition action add an "edit issue" action and edit the field "priority" to the the value you got from smart value of {{fieldChange}}.
Best
Stefan
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.
Add the smart value directly to this action, not after it. The action is executed when condition is true
so:
WHEN
THEN
Within the edit issue action for field "Priority":
This is currently set to "copy from current issue" --> change this to the smart value
You can click into this field and write your smart value into the field (see screenshot)
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stefan,
I've tried what you suggest before and found that, in When you can not enter "initiator is NOT member of group jira-admin". You only have some standard triggers, nothing related to groups of users.
I tried it the other way, but still no success.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I´m a bit confused. Weren´t you able to check this condition in your previous screenshot?
Best
Stefan
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.