unable to use flagged in Automation Rule

[Tasneem Abd El Hameed]

Idea

when flagged = impediment 

send a message to slack that we have a flagged cared 

and when flagged = empty  ( Removed)

send a message to a slack that the problem solved.

 Problem faced

here is the first step in Automation rule 

[Jack Brickey · Accepted solution]

disclaimer: I have not use "flagged" in any automation as yet.

looking at the log it seems to complain about multiple fields w/ the same name. I doubt, but could you verify that you don't have a custom field called Flagged that might be conflicting? In the meantime I will try to create a test rule and see what I can find.

it would also be interesting to add a "log" action and log the value for Flagged upon entry to the rule.

[Jack Brickey]

i did verify that the system Flagged field worked for basic rule....

[Tasneem Abd El Hameed]

Yeah i have two fields however they are both LOCKED  and unable to delete it

[Tasneem Abd El Hameed]

[Jack Brickey]

that is just weird. are you the site admin? do you have addons that might be adding this system field? You might need to contact Atlassian Support.

[Tasneem Abd El Hameed]

yes i am a site Admin, but how can i know which plugin that added these field , may be i can try to remove this plugin ?

[Jack Brickey]

to be honest I have no idea. Can you tell me which addons you have. With that I could inspect the Marketplace and see if any strike me as a possibility. Now it may not be an addon but I cannot understand how you would have a locked field otherwise. IMO, I cannot imagine why an addon vendor would use a field that is already 'reserved' w/in Jira itself.