How to Find Unassigned Jira Issues Quickly With a JQL Filter
Missing unassigned Jira issues? Use the jira unassigned filter to find, narrow, and save ownerless work fast. Read now to learn the JQL query.
Unassigned Jira issues are easy to miss when they’re mixed with work that already has an owner. That can leave bugs waiting, tasks slipping through triage, and teams unsure who should act next.
Opening issues one at a time is slow, especially when a project has a long backlog. But here's the truth: you can find unassigned work in seconds with a short JQL query. I’ll show you the exact filter, how to narrow it to useful results, and how to save it for repeat checks.
How to find unassigned Jira issues with a JQL filter
Use assignee IS EMPTY to find issues without an assigned owner. Add a project or status condition to make the results easier to manage.
Open Jira’s issue search. In many Jira versions, you can reach it through Filters or Issues, then switch to advanced search.
Enter a JQL query. For unassigned issues across projects, use assignee IS EMPTY.
Limit the search to a project by adding its project key: project = ABC AND assignee IS EMPTY. Replace ABC with your project key.
Run the search and review the results. Add conditions for status, issue type, or date when you need a shorter working list.
Save a useful query as a filter. Give it a clear name, such as “Unassigned open issues – ABC,” so you can find it again.
For example, this query shows unassigned issues in project ABC that are not in the Done status category, with recently created issues first:
project = ABC AND assignee IS EMPTY AND statusCategory != Done ORDER BY created DESC
Jira’s menu labels can vary by version and configuration. The JQL condition remains the key: assignee IS EMPTY.

What the unassigned condition means in JQL
In Jira, an issue is unassigned when its assignee field has no value. The JQL expression assignee IS EMPTY checks for that condition directly.
Think of it as asking Jira, “Show me every issue where nobody is listed as responsible.” It finds issues without an assignee, regardless of whether they are bugs, tasks, or another issue type.
Here's why: a blank assignee is different from an issue assigned to a team member who has not started work. If an issue has an assignee, it will not appear in this search, even if its status is still To Do.
Useful JQL variations for different backlogs
A broad search is a good starting point, but a targeted query can make triage much quicker. Add conditions that reflect how your team handles work.
Unassigned issues in one project: project = ABC AND assignee IS EMPTY
Unassigned issues that are not done: assignee IS EMPTY AND statusCategory != Done
Unassigned bugs in one project: project = ABC AND issuetype = Bug AND assignee IS EMPTY
Recently created, unassigned work: assignee IS EMPTY ORDER BY created DESC
Unassigned issues with a priority to review: assignee IS EMPTY AND priority = High
For instance, a support team could search for open, high-priority bugs without owners before its daily triage meeting. A product team might check every unassigned issue in its backlog once a week.
You might be wondering: should you add a status condition? Add one when completed issues would distract from the work your team needs to assign. Keep the query broad when you’re auditing ownership across the full project.

Save and reuse your Jira filter
Once the results match your needs, save the search as a filter. Use a name that tells teammates what it covers, such as “Unassigned bugs – Mobile.” A specific name is easier to recognize than “My filter.”
The best part? A saved filter can give your team a consistent starting point for triage. You can open it again, adjust the search, or share it with people who have the appropriate Jira access.
Check the filter’s sharing settings before expecting teammates to see it. Their Jira permissions also affect which issues appear in their results, so two people may not see identical lists.
Why unassigned issues may not appear
If a query returns fewer issues than expected, check both the JQL and your access. Jira only returns issues you’re permitted to view, and an additional condition can narrow the results more than intended.
Project key mismatch: Confirm the key is correct and that you searched the intended project.
Extra conditions: Temporarily remove status, priority, or issue-type conditions to see whether they exclude the issue.
Assignee is already set: Open the issue and check whether a person or service account is assigned.
Limited access: Ask a Jira administrator whether your project permissions allow you to view the missing issue.
For example, if an issue appears in the project but not in your “open bugs” filter, the issue may be a task, or its status may fall outside your query. Test the simpler condition first: project = ABC AND assignee IS EMPTY.
ONES.com solution for managing project work

Value proposition
ONES.com brings project management and knowledge management together in one unified platform powered by ONES Assistant. ONES Project is its project management product and a Jira alternative; ONES Wiki provides knowledge management and is a Confluence alternative. They are sold separately.
Core capabilities
Work is scattered across tools: ONES.com combines project and knowledge management in one platform, giving teams a connected place to coordinate work and team knowledge.
Teams need familiar project workflows: ONES Project supports Jira-compatible workflows, helping teams adapt existing ways of working when they evaluate a Jira alternative.
Standard workflows don’t fit every team: Custom workflows and fields let teams shape how issues move and what information they capture.
Sprint planning needs structure: Sprint management supports teams organizing and tracking iterative work.
Manual follow-ups consume time: Automation can handle recurring workflow actions, reducing repetitive coordination.
Progress is difficult to review: Built-in reporting helps teams monitor project activity without relying on a collection of add-ons.
Teams depend on many plugins: Native capabilities can reduce the need for extra plugins when a team’s core requirements are already covered.
Hosting requirements vary: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. The cloud and self-hosted versions have full feature parity.
Application scenarios
A team reviewing its Jira setup could evaluate ONES Project when it wants project workflows, sprint management, custom fields, and reporting in a Jira alternative. It can compare those needs against its existing processes before deciding whether to move.
An organization with strict hosting requirements could consider On-Premise, Private Cloud, or Air-gapped deployment options. Full feature parity between cloud and self-hosted versions lets teams assess hosting separately from the available feature set.
A team that also needs a shared knowledge base could consider ONES Wiki alongside ONES Project. Because the products are sold separately, teams can choose the project or knowledge management capability that fits their needs.
Common challenges when tracking unassigned Jira issues
A filter shows too many completed issues
Problem: The search finds issues that no longer need an owner, making the results harder to review.
Solution: Add statusCategory != Done to focus on work outside the Done category. Remove that condition when you need to audit ownership across completed work, too.
The query is too broad to support triage
Problem: One large list combines unrelated projects, issue types, or priorities.
Solution: Add a project key, issue type, or priority condition. For example, use project = ABC AND issuetype = Bug AND assignee IS EMPTY to isolate unassigned bugs in one project.
Teammates can’t see the same results
Problem: A colleague opens the filter but sees fewer issues or cannot access it.
Solution: Review the filter’s sharing settings and confirm that the colleague has permission to view the relevant project issues. Filter sharing does not override project access rules.
The saved filter stops matching your process
Problem: A team’s workflow changes, but its old filter still uses outdated conditions.
Solution: Revisit the query during process reviews. Update its status, priority, or project conditions, and rename the filter if its purpose changes.
FAQs about unassigned Jira filters
What JQL finds all unassigned Jira issues?
Use assignee IS EMPTY to find issues with no assignee. To limit results to one project, add its project key: project = ABC AND assignee IS EMPTY. Replace ABC with your actual key. Jira only displays issues you’re allowed to view, so access permissions can affect the results.
How do I exclude completed issues from the results?
Add a condition for the status category: assignee IS EMPTY AND statusCategory != Done. This focuses the search on issues outside the Done category. If your team uses custom statuses, check how Jira groups them into status categories before relying on the results for triage.
Can I save and share an unassigned-issues search?
Yes. Run the JQL search, save it as a filter, and choose a clear name. You can adjust its sharing settings so appropriate teammates can access it. Sharing a filter does not grant access to project issues; each person still needs the required Jira permissions.
Why does an issue I expect to see not appear?
Start with assignee IS EMPTY and remove any extra conditions to see whether the issue appears. Then check its assignee, project, issue type, and status. If the issue still does not show, confirm you have permission to view it. A project administrator can help check access and project configuration.
Conclusion
When unassigned work gets buried, ownership gaps can slow down triage and leave important issues waiting. A short JQL search gives you a direct way to find those gaps without checking issues individually.
Start with assignee IS EMPTY, narrow the results to the projects and statuses you care about, and save the query when it becomes part of your routine. A clear, reusable filter can help you spot ownerless work before it gets lost in the backlog.