How to Filter Issues by Status Name Using JIRA REST API

Other Questions Jira
1

I’m working with JIRA’s REST API and need to find all tickets that have “In Progress” status. When I look at the status object, it has this structure:

"status": {
  "self": "https://company.jira.com/rest/api/2/status/3",
  "description": "This issue is being actively worked on at the moment by the assignee.",
  "iconUrl": "https://company.jira.com/images/icons/statuses/inprogress.png",
  "name": "In Progress",
  "id": "3",
  "statusCategory": {
    "self": "https://company.jira.com/rest/api/2/statuscategory/4",
    "id": 4,
    "key": "indeterminate",
    "colorName": "yellow",
    "name": "In Progress"
  }
}

Right now I have to use the status ID in my JQL query like this:

https://company.jira.com/rest/api/2/search?jql=project=TESTPROJ and status=3 and component=12345&fields=id,key,summary,status

Is there a way to use the actual status name “In Progress” instead of the numeric ID in my query? It would make the code much more readable.

2

yep, you can totally use the status names! just put them in quotes like this: status="In Progress" instead of the id. your query would look like project=TESTPROJ and status="In Progress" and component=12345. way simpler to remember!

3

Hit this exact problem last month when our admin changed status IDs during a workflow update. Status names work great like everyone said, but heads up - if your status has multiple words or special characters, wrap it properly. “In Progress” with quotes is fine, but I had a custom status “Ready-for-Review” that broke until I escaped it right. Pro tip: use the IN operator for multiple statuses: status IN ("In Progress", "Code Review"). Way cleaner than chaining a bunch of OR statements with IDs.

4

The status name approach works great in JQL queries. I’ve used this for years - way more maintainable than hardcoding IDs. Your query becomes project=TESTPROJ and status="In Progress" and component=12345. Just remember status names are case-sensitive and need exact matches including spaces. Custom statuses with special characters might need proper escaping. Big advantage: your queries stay valid even when status IDs change during JIRA migrations or config updates. This has saved me tons of debugging time.