I am wondering this too. Can we use JQL to search for "Flagged" issues?

Edit: Figured it out; "Flagged = impediment"

Is it possible to JQL flagged issues?

La requête #991064 - [JIRA] (GHS-4544) As a (Scrum) Rapid board user, I need to flagissues as impediments a été crée.

Pour effectuer un suivi, et/ou ajouter un commentaire, veuilliez répondre à ce courriel.
Cette requête sera traitée dès que possible.

Merci de votre collaboration,Your request 991064 - [JIRA] (GHS-4544) As a (Scrum) Rapid board user, I need to flagissues as impediments has been created.

For a follow-up, and/or add comments, please reply to this e-mail.
This request will be treated as soon as possible.

Thank you for your cooperation,

Votre requête / Your request
Kranti Bandi commented on GHS-4544 As a (Scrum) Rapid board user, I need to flag issues as impediments Perfect! Thanks for this modification! I like the way you highlight the stories. I would really like to dig into this more. This message is automatically generated by JIRA.If you think it was sent incorrectly, please contact your JIRA administratorsFor more information on JIRA, see: http://www.atlassian.com/software/jira

Perfect! Thanks for this modification!

I like the way you highlight the stories. I would really like to dig into this more.

This was released in version 6.2.3 - tracked on the related issue GHS-5875

La requête #983949 - [JIRA] (GHS-4544) As a (Scrum) Rapid board user, I need to flagissues as impediments a été crée.

Pour effectuer un suivi, et/ou ajouter un commentaire, veuilliez répondre à ce courriel.
Cette requête sera traitée dès que possible.

Merci de votre collaboration,Your request 983949 - [JIRA] (GHS-4544) As a (Scrum) Rapid board user, I need to flagissues as impediments has been created.

For a follow-up, and/or add comments, please reply to this e-mail.
This request will be treated as soon as possible.

Thank you for your cooperation,

Votre requête / Your request
Andrew Clarson commented on GHS-4544 As a (Scrum) Rapid board user, I need to flag issues as impediments used to have this on "legacy boards" , seems to have been lost in latest version - can we get this feature back asap as flagging impediments is a core feature of scrum This message is automatically generated by JIRA.If you think it was sent incorrectly, please contact your JIRA administratorsFor more information on JIRA, see: http://www.atlassian.com/software/jira

used to have this on "legacy boards" , seems to have been lost in latest version - can we get this feature back asap as flagging impediments is a core feature of scrum

Hey all, here are couple easy ways to do this:

Make a label called "flag" and associate it to a bright card color. Now each card with that label will stand out.

What we've also done is create a swim lane called 'blocked' and associate it to a label called 'blocked'.

I'm still getting used to the upgrade, installed this past weekend. Being able to flag impediments in a minimum number of keystrokes is very important to our multi-team project.

More votes for Impedement flag (and other custom flags if possible). We recently moved to Ondemand with this new greenhopper hoping that atlassian does support kanban better. But thanks to the missing flag we are seriously looking for moving away from Atlassian (the biggest plus to stay is that we are NOT looking forward to a migration project at all)

I agree with all of the above, impediment flag is a must have on the new board..

We also need the impediment flag. The workaround is to install a complicated workflow with specific statusii, so we can see blocked tasks. However, this is not an option for us. Can't really use RB until this is added

We need to be able to block items on the board. Would like to be able to add a comment and have the date/time saved. Both for when the block is put on, and when the block is taken off again.

Blocker for our Product Organization to use the new boards...

Until now, we cannot use RP without that feature!

Yep, it's a "Must have"

It would be useful that if a task is flagged as impediment than it isn’t be added to WIP limit.

This is a "must have" if you will use the Rapid board as a Kanban-board.

Please add me to the votes to get this feature added. We really need to be able to flag something that is impeded/blocked from the Rapid board on our team. It would be nice to also be able to leave a comment at the same time it's flagged for context behind why it's blocked. As a workaround we are using the "Blocker" Priority state to show things that are blocked, but it is a workaround and the Priority field shouldn't normally be used in this manner.

Seems like this feature has been asked for in multiple ways (see linked tickets). Some like GHS-2268 are more general solutions. This ticket is not general but is a simple replacement for the functionality that was present on the existing planning/task boards.

It would be nice to get this in the short term so more teams that need this feature can migrate from the existing boards to the Rapid board and in the long term GHS-2268 seems like it will make everyone happy.

This looks to be the only missing item from the existing Planning/Task boards. Every other difference between the existing boards and the new Rapid board can be accomplished some other way but there is NO WAY to flag or unflag anything on the Rapid board.

It would be acceptable to add Flag/Unflag to the edit screen for an issue, however it is a MUST that flagged issues be indicated somehow on the new Rapid board. Ideally it would be easy to flag and unflag right from the Rapid board without going to an edit screen.