Check Flagged field automation JIRA

[Tasneem Abd El Hameed]

Hi All, 

Please find my automation rule that i created, and it is not working please advice

[John Funk · Accepted solution]

Hi Tasneem,

Since you have the two flagged fields, you might take this one out and use the other to see if it helps in the short term. You definitely need to report the two fields to Atlassian. 

[Tasneem Abd El Hameed]

yess, i will report it thanks John

[Jack Brickey]

Please report back here if you don’t mind. I’m keenly interested in cause. Maybe an addon is using this field name…unsure.

[Tasneem Abd El Hameed]

@Jack Brickey  @John Funk  they fixed to me, but they were assuming that this problem happened due to  the restoration of a cloud instance or merging two cloud instances.
Both of the fields were created  that leads them to assume it was a migration from the server to cloud migration.

Reoccurrence of this issue is unlikely unless you do it manually or perform an instance restoration.

and this happened before joining this company, 

Thanks John and Jack for your support :)

[Jack Brickey]

Thanks for letting us know!

[Jack Brickey · Accepted solution]

What does the audit log indicate for a triggered rule that you would expect to succeed?

[Tasneem Abd El Hameed]

it gave  me error as i have two similar field for "flagged" and i found them locked, so how can i fix this ?

[Jack Brickey]

Ah so do you have a custom field “flagged”? If so I highly recommend not doing that. You really should never create a custom field named the same as a system field. This is a good example of why. As John mentioned you may want to open a ticket with Atlassian just to report this. However I suspect the answer will be to change the name of your custom field.

[Jack Brickey]

Oh…I see in your other related post that you are showing two system fields labeled flagged. Sure seems odd and agree to report to Atlassian.

[Tasneem Abd El Hameed]

aaah, right i will open a ticket thanks Jack :)