Use automation to flag issue

[Robbert Tuerlings]

I want to have all issues that exceed the Original Estimate Value to be Flagged.

[Robbert Tuerlings · Accepted solution]

@Bill Sheboy @Bayan Hashem 

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!

[Bill Sheboy]

Thanks, @Robbert Tuerlings 

That seems like a recent/pending change as it still works for me with just TRUE.

[Robbert Tuerlings]

It sure does. Since we both are running Cloud, we could be running different versions without our knowledge.

Now you know what to do whenever your field is updated as well :)

[Bayan Hashem]

@Robbert Tuerlings Thank you, its worked with me (use "Impediment " value in "Edit issue" action)

[Richard Johnson]

Answer needs an update for current version of Jira so here it is:

On the last step (Edit issue fields) set flagged = impediment.

[Brooke]

Is there a way to use automation to also remove the flag? 

[Bill Sheboy]

Hi @Brooke 

Yes, you can edit the issue, selecting the Flagged field and leaving the value empty.

Best regards,
Bill

[Bayan Hashem]

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.

[Bill Sheboy]

Hi @Bayan Hashem 

Would you please explain the reason for the changes you are recommending?  I didn't need to do either of those things to get the rule to work.  It seemed that @Robbert Tuerlings was not able to see all of the available options in the drop-down list when setting the Flag.

Thank you.

[Robbert Tuerlings]

Hey @Bill Sheboy 

The issue is that the comment, that is the follow-up rule, is added to the task. Whilst the same task isn't updated to reflect being "Flagged" by the same automation.

Thanks!

[Bill Sheboy]

I just tried this with a simple rule and it worked for me:

• Trigger: transitioned (status changed)
• Condition: story points not empty
• Action: set Flagged to TRUE
• Action: add a comment

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.

[Robbert Tuerlings]

That sounds like you have got it figured out.

Where I am lost is: "set Flagged to TRUE" - could you perhaps share more info (e.g. screenshot) what options are used for this?

See the following as my current setup.

[Bill Sheboy]

Hi!  Please see below for my example.  In your field edit to set Flagged, try looking in the drop-down list for TRUE.  I did not need to use the More options area.

[Robbert Tuerlings]

Hey Bill,

Not sure what is happening here, but I cannot see that option.

These are my results - I've tried re-adding the option, still the same.

And the project is "Classic software project".

[Bill Sheboy]

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.

https://support.atlassian.com/contact/#/

Once they answer your issue, would you please post back to here the resolution?

Thanks!

[Robbert Tuerlings]

Hey Bill,

Thanks for the link. I will update this thread once I have an answer from them.

[Bayan Hashem]

Hello,

Please I need to check the update of this issue

[Robbert Tuerlings]

Removed.

[Bill Sheboy]

Hi @Robbert Tuerlings 

What is the issue you are seeing trying to add/run this rule?

Best regards,

Bill