Confluence logoConfluenceTeamLens for Confluence

How do you show Jira work items with no assignee, estimate or due date on a Confluence page?

How do you show Jira work items with no assignee, estimate or due date on a Confluence page?

Planning goes wrong quietly. The work item with no assignee is nobody's job, the one with no estimate is missing from the capacity sum, and the one with no due date never shows up on the release page. A Confluence page can list all three live from Jira with nothing installed: each gap is one IS EMPTY query in the Jira work items macro.

Short answer: add a Jira work items macro per gap, each with a JQL query that keeps only open work and tests one field for no value: assignee IS EMPTY, due IS EMPTY and originalEstimate IS EMPTY (or your story points field), each with AND statusCategory != Done. Atlassian's JQL keywords reference describes EMPTY as the way "to search for work items where a given field does not have a value". Switch a second copy of each macro to the count view for a row of headline numbers. What the native macros cannot do is show the gaps side by side per project or per Atlassian team in one table.

One query per gap

GapJQL (add your project scope in front)Notes
Nobody owns itassignee IS EMPTY AND statusCategory != DoneAssignee supports IS and IS NOT
No due datedue IS EMPTY AND statusCategory != Donedue has the alias dueDate; Atlassian's own example is duedate is empty
No time estimateoriginalEstimate IS EMPTY AND statusCategory != DoneOnly when time tracking is on; alias timeOriginalEstimate
No story points"Story point estimate" IS EMPTY AND type in (Story, Task, Bug) AND statusCategory != DoneUse the name of your points field; custom number fields support IS and IS NOT

All four rest on the same rule from the keywords reference: EMPTY "can only be used with fields that support the IS and IS NOT operators", so check a field's entry in the JQL fields reference before you rely on it. EMPTY and NULL mean the same thing, and the operators page gives fixVersion is empty or fixVersion is null as the pattern.

Two details that trip people up:

Leave out the estimate row for epics and sub-tasks if your team only estimates stories, tasks and bugs; that is what the type in (...) clause is for.

Put it on the page

  1. Edit the Confluence page, type /jira and choose the Jira work items macro.
  2. Select JQL instead of the default basic search and paste the first query with a scope, for example: project in (APP, WEB) AND assignee IS EMPTY AND statusCategory != Done ORDER BY created ASC
  3. Pick the columns. Atlassian's macro page: "Choose the columns you want to appear by selecting the column icon", and you can drag them to reorder. Key, summary, status, created and reporter are enough to chase an owner.
  4. Insert a copy and select COUNT VIEW, which shows "just the number of work items". Put the count macros side by side in a table row at the top of the page: unassigned, no due date, no estimate.
  5. Repeat for each gap, then publish. Each macro is a live query, so the list shrinks as people fix the work items.

If the page is for one team, put the team scope in front of every query (a filter, a project or a component). A page with three gaps for four teams is twelve macros, and each one is edited by hand when a team changes.

What the native macros do not show

For a one-project page that only needs "who owns this?", stop here: one assignee IS EMPTY macro does the job and costs nothing.

How TeamLens for Confluence fits

We make TeamLens for Confluence, a Confluence macro on the Atlassian Marketplace that reads Jira work from the same site. One of its five reports is Hygiene: open work that is missing ownership or planning data, per project. Its tiles show open work items, work with no team, stories, tasks and bugs with no estimate (when a story points field exists) and work with no due date; the table has a row per project with the no-team count and percentage, no estimate and no due date, and below it up to 50 open work items with no team. You insert it with /TeamLens, pick Hygiene and choose a scope (Jira projects or any JQL).

Its limits: it reads only the Jira on the same Atlassian site, counts up to 3,000 work items per macro, shows a placeholder in PDF and Word exports, and viewers without Jira access see a "No access to Jira" message. Each viewer loads the report with their own Jira permissions through one read-only scope (read:jira-work); there is no backend and no storage. It is free for sites with up to 10 users. Details: the TeamLens for Confluence page. For work that is assigned but not moving, see stale Jira work items on a Confluence page; for team grouping, Jira work by team on a Confluence status page.

FAQ

What JQL finds unassigned Jira work items?

assignee IS EMPTY. Add AND statusCategory != Done to leave out finished work. assignee IS NULL returns the same result.

What JQL finds Jira work items with no due date?

due IS EMPTY or duedate is empty, the example in Atlassian's JQL keywords reference.

How do I find Jira work items with no estimate?

For time estimates, originalEstimate IS EMPTY (only when time tracking is enabled). For story points, "Story point estimate" IS EMPTY or cf[<field id>] IS EMPTY, using the name or ID of the points field on your site.

Does != empty find fields with no value?

No. != empty matches work items where the field has a value. Use IS EMPTY for no value and IS NOT EMPTY for any value.

Can a Confluence page show these counts without an app?

Yes: the Jira work items macro has a count view. You need one macro per gap and per scope, and there is no built-in percentage or side-by-side table.

Sources

  1. JQL keywords, Atlassian Support - EMPTY and NULL, the IS / IS NOT rule, the duedate is empty example. Read 18 Oct 2026.
  2. JQL operators, Atlassian Support - IS and IS NOT with EMPTY or NULL, the fixVersion example. Read 18 Oct 2026.
  3. JQL fields, Atlassian Support - Assignee, Due (alias dueDate), Original estimate (time tracking, alias timeOriginalEstimate), Custom field (name or cf[ID], the location != empty example); no Team entry. Read 18 Oct 2026.
  4. Display Jira work items in a list, Atlassian Support - JQL search, COUNT VIEW, choosing and reordering columns. Read 18 Oct 2026.
  5. Insert the Jira chart macro, Atlassian Support - pie chart segment fields. Read 18 Oct 2026.
  6. JRACLOUD-87808, Team field not supported for sorting on gadgets, JQL or boards - Gathering Interest, 651 votes on 18 Oct 2026.

Related reading

Confluence logoConfluenceTeamLens for Confluence

How do you show Jira team workload on a Confluence page?

· 4 min read

Native Confluence macros chart Jira work by assignee or status, not by Atlassian team. What the Jira chart and Jira work items macros can show, the JQL for one team's open and overdue work, and a live per-team workload table. Checked 30 Oct 2026.

Confluence logoConfluenceTeamLens for Confluence

How do you show Jira team velocity on a Confluence page?

· 4 min read

Jira's velocity chart lives on one scrum board and the Confluence Jira chart macro has no velocity chart. What you can put on a page with native tools, where the numbers differ, and a per-team velocity table across boards. Checked 23 Oct 2026.