Can you trust the numbers in Jira?

Jira is work tracking software where teams plan, assign and follow their work, including work handed to AI agents. Its own help pages give 3 reasons its numbers can look different from what you expect. The first to rule out: Work a team has finished can still count as open in Jira's reports if nobody set its Resolution field, as Atlassian's support pages explain.

Wins · Are they booking and buying?

Is it broken, or just counted differently?

A number can look wrong because the business changed, or because of how Jira counts it. Below is what Jira keeps, where its help pages say the numbers can differ, and how to check them yourself.

What does Jira keep track of?

  • Jira keeps built-in reports that chart how work items and projects move over time.

    In Jira's own words: Jira reports let you visualize trends about your project, versions, epics, sprints, and issues. How to use Jira reports and dashboards, read 2026-11-12.

  • Jira keeps dashboards of work figures that one person can keep to themselves or share with the team.

    In Jira's own words: Dashboards can be private or shared with other users on your instance. How to use Jira reports and dashboards, read 2026-11-12.

What can make Jira's numbers look wrong?

  1. Work a team has finished can still count as open in Jira's reports if nobody set its Resolution field, as Atlassian's support pages explain.

    In Jira's own words: Without a resolution value, the ticket is treated as 'unresolved,' which may cause confusion when interpreting reports. Best practices on using the "Resolution" field in Jira Cloud, read 2026-11-12.

  2. Atlassian's support pages describe cases where Jira's Created vs. Resolved chart shows no resolved items or the wrong count, tied to how the Resolution field is set up.

    In Jira's own words: The chart is showing 0 issues being resolved or the resolved issues count is incorrect. Jira Cloud - Created vs. Resolved chart showing incorrect count of resolved issues, read 2026-11-12.

  3. A download of work items from Jira can be capped, as Atlassian's support pages explain, so a total counted from one file may leave items out.

    In Jira's own words: Each batch export has a maximum limit of 1,000 work items. Export over 10,000 work items in Jira Cloud, read 2026-11-12.

How do I check Jira's numbers myself?

  1. To count a long list in full, split a Jira search into smaller parts, such as date ranges, and download each part.

    In Jira's own words: Use JQL to divide your search results into smaller batches of fewer than 10,000 work items each. Export over 10,000 work items in Jira Cloud, read 2026-11-12.

  2. Searching for work items in Jira shows Unresolved on any item with no resolution set, which helps spot finished work that reports still treat as open.

    In Jira's own words: The Issue Navigator displays "Unresolved" when no resolution is set for an issue. Best practices on using the "Resolution" field in Jira Cloud, read 2026-11-12.

How does Jira work with Feder?

Connect Jira to Feder and it joins your Wins apps. Feder only reads. It never changes anything in Jira.

When you connect Jira, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.

Other apps that feed Wins

Questions owners ask about Jira

See every connection.

Where do these answers come from?

Everything this page says about Jira comes from Jira's own pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.

Know the day a number breaks, not the month after.

Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.