Hi all, does anyone know of an equivalent feature request for Jira Cloud? And if so could you please share/link with this one? I could only find JSWCLOUD-21694 Allow changing the value for the field Flagged, which seems to be much more recent.

we have the same request and this is 6 years since the original request in this thread. we need a visual way to indicate particular types of impediment, sure we can use a field inside the ticket and maybe change the colour of the ticket, but we already use ticket colour to re-enforce the priority of a ticket because as someone said it is quite weak at attracting our teams attention to it

+1
We have currently the same request for our teams. It would improve their priority management which would be really usefull. 

This feature would very much be appreciated. Atlassian did add the "Add Flag and add Comment" feature to the right click context sensitive menu to the cards on boards, which helps to speed up the flow, but a comment is still unstructured data and we'd like to be able to create dashboards with specific types of impediments (as there are different people tackling different types of impediments)

+1 as well.

I see that JIRA's flagged field appears to allow multiple options:

Has anyone tried adding more than the single "impediment"?

+1 for this big time. Would be really great for our team.

Agree flagged field could be improved by adding single select feature that each client configures to track types of blockers or reasons for blockers. This would help not only teams but entire organizations understand where they have the most opportunities for improvements and reduce blocker types. for example. Hope you just do something that 1) keeps the flag visible when someone adds it, but then enables a team to select a reason or type. This aspect should be configurable by the Jira Admin team for each client. Also, this should be editable in the details screen on the right side of the board, so teams don't have to open up the issue type to edit or select the reasons.

+1 - I am looking for this

We have multiple groups which cross projects. There can be bi-directional dependencies. Configurable flags would be helpful in identifying and filtering these issues.
Links are OK, but, not easily seen on the boards.
Example:

• Flag 1 - Group A depends on Group B to finish this
• Flag 2 - Group C depends on Group A to finish this

Yes please, +1 for multiple flag types. Thanks!

This feature is essential for us. Its absence is making us investigate external Kanban boards.

+6 Multiple flag types would be very helpful.

Currently we use flags to indicate blocked in product backlog, blocked in sprint backlog, At Risk for going back in sprint backlog.

Other uses cases have been discussed but the flags are so overloaded now we often turn to labels which are not as visually satisfying.

+5 for multiple flag types, or even be able to configure what the default flag determines e.g. As opposed to Impediment, alter to read Ready, or whatever is applicable.

+4 it will be useful if issue is going back to TODO column from code review or testing.

+3 - Having multiple flag colors or types would be very handy. Right now on my Kanban board it's not easy to see which stories are flagged for which impediments.

+2

+1 for multiple flag types

Currently it's really a pain that jira does not support green flags to mark a story as ready - and thus support a kanban pull principle.

Brilliant, thanks mjopson. Have a super day!

Hi njm ,
Unfortunately, there's no way to currently do this, I've created a new story:
https://jira.atlassian.com/browse/GHS-9450
Thanks
Martin

Hi mjopson, quick question,

Do you know of a way to JQL search for something that was flagged?

For instance, a Kanban team may use the flag on an issue (or several over time) and then want to look at their cycle time while excluding issues that were ever flagged. We can exclude the currently flagged issues with Flagged ~= Impediment.

Unfortunately Flagged WAS "Impediment" does not work as it is a 'Multi Checkboxes' custom field and they do not support WAS JQL (nor does the CHANGED clause).

Know any way to make that work? What am I missing?

Thanks, have a super day,
Nick

Thanks mjopson - using it at Twitter now and it is fabulous!

Please note that basic flagging of issues was released in version 6.2.3 - tracked on the related issue GHS-5875.
This may solve many use-cases.

rgibbons thanks for the blogs and suggestions. They've come in handy!

Just realized that flagging does not appear to exist in the new rapid board. We miss this feature.

Hey guys, I have had many of these same issues with not being able to flag tickets, or needing more information about why something was flagged. Here are links to some of my solutions: Dealing with Impediments on the Rapid Board and Using a custom field to give more information about what is impeded. Hope this helps in the interim.

Ditto for me as well...I would like to add to this field with different flag types, as a highly visible temporary condition within a Status, currently accomplished with additional (alternate) columns (Statuses). Also, please add this field to the Rapid Board in the same way it is used in the other boards.

I too would like a comment or way to categorize flags. As a developer, I'd like to say "My card is blocked because [list of values]" As a manager, I'd like to get email or IM notificiation whenever a flag is set so that I can bring all resources to bear on the blocking issue. Right now staring at the board and refreshing it every so often is the only way I can see where things block, and that's not very efficient.

Would it also be possible to have the option of entering a comment while setting a flag?
Example: i select the Flag command, a screen pops-up with the type of the flag, and i have the comment field.
That would be a nice feature that would allow to enter a reason why an issue has been flagged.

+Vote

Supporting multiple types of flag option is really high demand feature from our distributed teams to indicate their bottleneck visually.

My company is starting to track impediments as a metric, to try to identify various causes of impediments and systematically eliminate them. We are currently using labels to "tag" an issue when an impediment is hit (i.e. "Waiting", "Requirements change", etc). We thought we could use the GH "Flag" instead, since the interface is so easy from the Planning/Task boards, but there is no way to choose the type of flag. This improvement would make tracking this "impediment" metric much easier for us, please implement it!

As an implementation idea, if the "Flag" custom field that is configured has only one choice, then I would leave the current interface alone (simple boolean). If the custom field has multiple choices, then either implement a sub-menu from the "cog" menu (i.e. click "cog", click "Flag", choose type of flag from submenu) or a pop-up dialog to choose the type of flag (similar to how it works for Comment).

Yes, more flag iconography, and flagging options is something I look forward to.