This is the answer of support:
Currently, the custom field flagged is locked and cannot be modified. So you cannot add any context to add True or false. This was present in the past however, due to issues in flagging, this field is now changed in such a way that context cannot be added and the default value is impediment.
To achieve your use case, you have to use "Impediment " value in "Edit issue" action. This should work.
I've updated the field as such and it did work!
I just tried this with a simple rule and it worked for me:
I see a note for your field edit of Flagged, Advanced. What are you trying to set the field to?
And, what does the audit log say is happening?
Thanks for any additional info.
That is curious... At this point, I recommend submitting a support ticket to Atlassian and have the automation folks take a look. You are site admin, so you should be able to submit the ticket directly.
Once they answer your issue, would you please post back to here the resolution?
Actually its worked and you need to fill "Impediment " value in "Edit issue" action. And if you need to run based on another rule check the following checkbox in Trigger section:
Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events