You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
What ist the JQL to find the issues which have a flag in the backlog?
Flagged = Impediment from the descrpition in https://confluence.atlassian.com/agile/jira-agile-user-s-guide/working-with-issues/flagging-an-issue *does not work*
The Flagged item is a strange one.
To check if an item is flagged or not use
Flagged is EMPTY
Flagged is not EMPTY
Admin rights don't matter to what you can or can't see on issues. Project rights determine that.
This error message means either that the field does not exist, or it is not used in any project you can see.
Do you have Jira Software installed, and have you got access to at least one Software project?
Hi @Sarah Ahmed
You'll notice in my earlier reply that I use an uppercase F for Flagged, whereas you're showing flagged. The Jira field names are case sensitive. If you go into the filter screen and start typing flag then the "intellisense" will tell you what the correct wording is (see below), but obviously for other languages typing flag won't work.
I just tried
project = "X" AND issuetype in (Story) AND Flagged is not EMPTY ORDER BY updated DESC
and I get a list of issues that were flagged, and the number of days listed in the "Flagged" field next to the word "Impediment".
I would think that the search you're suggesting would work about the same as any other field's history of values.
Try using the WAS operator in your search.
WAS" operator is used to find issues that currently have or previously had the specified value for the specified field.
Flagged WAS not EMPTY
Flagged WAS Impediment
I've just found out (under Jira DC 8.18.0) that "Flagged" is created when the first issue gets flagged. For the name, it will use the language that the user who flagged the issue is currently using.
Before that, there will be no such field.
The "Flagged" field must be on a screen in your project in order for a JQL search on it to work.
You can still add a flag to an issue using an agile board and right clicking the issue, but you cannot filter by the field unless you have it on a screen.
If it is on a screen, you can also "flag" an issue by updating the field's value to check the Impediment checkbox that appears when you edit the field value.
JQL could be:
Flagged is not EMPTY
Someone on our team also figured out that if you have more than the default field context on the Flagged field, the search won't work, even if the field is on a screen in the project.
It's a bug.
The person on our team looking into this issue discovered that he had not checked a basic setting, although the context thing may still be a bug. I'm not sure.
In the Field Configuration, the Flagged field was set to hidden, because we had it visible previously, but then had to remove it from screens. So, in a way to make it easier to update, someone just hid the field.
Moral of this story: check the basics first. :)
I had to actually flag an issue to make it work. Until an issue was flagged I got "Flagged" not found. And I used for a Flagged = Impediment. and it work perfectly after I flagged an issue.