According to https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-operators-reference-764478341.html#Advancedsearching-operatorsreference-WASWAS the operator "WAS" should be supported for the 'Status' Field.
But when trying the 'status was "in progress" ' query in issues on mycompany.atlassian.net I get "The operator 'was' is not supported by the 'status' field."
Any ideas?
This is/was a real bug in Jira Cloud JQL and the fixed will be rolled out in a few weeks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marcus,
It works fine for me project = ABC AND status was "In Progress" and I'm getting list of results
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Support! :)
Won't work for me "project = CONARAS AND status was 'in progress'" yields error on https://bitaddict.atlassian.net.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks Marcus, I see small typo in your query 'in progress'" - there is additional quotation marks and overal quotation marks are not used correctly - hence this is why you get error I presume.
try this project = "CONARAS" AND status was "in progress"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marcus,
do you have a custom field called "status"?
What happens, if you just type "status =" at the JQL field? Is the code completion showing the expected status in the dropdown?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomas,
I'm not sure. :) The dropdown only shows 'EMPTY' as a constant.
I've set up a Kanban board and added some custom statuses to get the right # of columns/statuses that work for us, but it was all done with help from Jira.
There is no 'Status' under Admin->Issues->Custom Fields at least. just ~15 others createc by Jira (Epic Name/Link/Color & whatnot).
Field Configurations only have "Default Field Configuration".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@support: Same result. I've tried with and without various quotation marks before asking the question, but the error message stubbornly remains.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Btw, thanks for the amazingly quick responses, guys. Much appreciated! :-D
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm, there seems to be something wrong with your status field. An issue can't have an empty status. That's impossible. It always has to be in a status of a workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you look at the field configuration of your instance (Admin section -> Issues -> Field Configuration -> Configure) - do you see a status field there?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nope. No Status field in the "Field Configuration".
Under Issue Attributes -> Statuses there are of course a number of status, some default, some added by me, used by different workflows
Is it because we used Jira to set up a custom-ish Kanban board/workflow for our project? It seems to be a bit dynamic somehow, which could cause that. It was last year so I don't remember the exact details though.
It sounds like I've ended up with a text 'status' field somehow, if I read your suspicions right.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that's is what I assume. Could you please run the following REST call:
<your Jira-URL>/rest/api/2/status
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have same error on our Jira Cloud instance
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anton,
I've just tested this in my Cloud test environment and didn't see that error.
Maybe you and Marcus should raise a bug at the official Atlassian support, since I am reaching the end of my options here.
Here you find official Atlassian support:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thomas,
This is the result of the REST call:
[ { "self":"https://bitaddict.atlassian.net/rest/api/2/status/3", "description":"This issue is being actively worked on at the moment by the assignee.", "iconUrl":"https://bitaddict.atlassian.net/images/icons/statuses/inprogress.png", "name":"In Progress", "id":"3", "statusCategory":{ "self":"https://bitaddict.atlassian.net/rest/api/2/statuscategory/4", "id":4, "key":"indeterminate", "colorName":"yellow", "name":"In Progress" } }, { "self":"https://bitaddict.atlassian.net/rest/api/2/status/4", "description":"This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.", "iconUrl":"https://bitaddict.atlassian.net/images/icons/statuses/reopened.png", "name":"Reopened", "id":"4", "statusCategory":{ "self":"https://bitaddict.atlassian.net/rest/api/2/statuscategory/2", "id":2, "key":"new", "colorName":"blue-gray", "name":"To Do" } }, { "self":"https://bitaddict.atlassian.net/rest/api/2/status/10000", "description":"", "iconUrl":"https://bitaddict.atlassian.net/", "name":"Backlog", "id":"10000", "statusCategory":{ "self":"https://bitaddict.atlassian.net/rest/api/2/statuscategory/2", "id":2, "key":"new", "colorName":"blue-gray", "name":"To Do" } }, { "self":"https://bitaddict.atlassian.net/rest/api/2/status/10001", "description":"", "iconUrl":"https://bitaddict.atlassian.net/", "name":"Selected for Development", "id":"10001", "statusCategory":{ "self":"https://bitaddict.atlassian.net/rest/api/2/statuscategory/2", "id":2, "key":"new", "colorName":"blue-gray", "name":"To Do" } }, { "self":"https://bitaddict.atlassian.net/rest/api/2/status/10002", "description":"", "iconUrl":"https://bitaddict.atlassian.net/", "name":"Done", "id":"10002", "statusCategory":{ "self":"https://bitaddict.atlassian.net/rest/api/2/statuscategory/3", "id":3, "key":"done", "colorName":"green", "name":"Done" } }, { "self":"https://bitaddict.atlassian.net/rest/api/2/status/10003", "description":"This status is managed internally by JIRA Software", "iconUrl":"https://bitaddict.atlassian.net/", "name":"Ready to Test", "id":"10003", "statusCategory":{ "self":"https://bitaddict.atlassian.net/rest/api/2/statuscategory/4", "id":4, "key":"indeterminate", "colorName":"yellow", "name":"In Progress" } }, { "self":"https://bitaddict.atlassian.net/rest/api/2/status/10004", "description":"This status is managed internally by JIRA Software", "iconUrl":"https://bitaddict.atlassian.net/", "name":"Ready To Release", "id":"10004", "statusCategory":{ "self":"https://bitaddict.atlassian.net/rest/api/2/statuscategory/4", "id":4, "key":"indeterminate", "colorName":"yellow", "name":"In Progress" } }, { "self":"https://bitaddict.atlassian.net/rest/api/2/status/10006", "description":"This status is managed internally by JIRA Software", "iconUrl":"https://bitaddict.atlassian.net/", "name":"Archived", "id":"10006", "statusCategory":{ "self":"https://bitaddict.atlassian.net/rest/api/2/statuscategory/3", "id":3, "key":"done", "colorName":"green", "name":"Done" } }, { "self":"https://bitaddict.atlassian.net/rest/api/2/status/10007", "description":"This status is managed internally by JIRA Software", "iconUrl":"https://bitaddict.atlassian.net/", "name":"WontFix", "id":"10007", "statusCategory":{ "self":"https://bitaddict.atlassian.net/rest/api/2/statuscategory/3", "id":3, "key":"done", "colorName":"green", "name":"Done" } }, { "self":"https://bitaddict.atlassian.net/rest/api/2/status/10008", "description":"This status is managed internally by JIRA Software", "iconUrl":"https://bitaddict.atlassian.net/", "name":"Duplicate", "id":"10008", "statusCategory":{ "self":"https://bitaddict.atlassian.net/rest/api/2/statuscategory/3", "id":3, "key":"done", "colorName":"green", "name":"Done" } }, { "self":"https://bitaddict.atlassian.net/rest/api/2/status/10100", "description":"This status is managed internally by JIRA Software", "iconUrl":"https://bitaddict.atlassian.net/", "name":"Waiting To Release", "id":"10100", "statusCategory":{ "self":"https://bitaddict.atlassian.net/rest/api/2/statuscategory/4", "id":4, "key":"indeterminate", "colorName":"yellow", "name":"In Progress" } }, { "self":"https://bitaddict.atlassian.net/rest/api/2/status/10200", "description":"", "iconUrl":"https://bitaddict.atlassian.net/images/icons/statuses/generic.png", "name":"Ready to review", "id":"10200", "statusCategory":{ "self":"https://bitaddict.atlassian.net/rest/api/2/statuscategory/4", "id":4, "key":"indeterminate", "colorName":"yellow", "name":"In Progress" } } ]
If you can't find anything there, I'll take it up with support. Many thanks again for the help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marcus,
no, this looks good. You have some status (would be weird if you wouldn't) - but I don't know, why your JQL doesn't find them.
If you find a solution or a reason for the problem, post it here, if you want. It seems, there are other users also having this problem and it might help them. I am also interested in the reason for this problem :-)
Good luck
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.