Why did my resolved count in Jira suddenly jump?
The Jira help pages give 4 common reasons. The first to rule out: Resolving an item again moves its resolved date to the new day, so items reopened and closed again count on the later date.
Is it broken, or just quiet?
A number can fall because fewer people came, or because something stopped counting them. Below are the causes the Jira help pages give, and how to check each one yourself.
What causes it?
Resolving an item again moves its resolved date to the new day, so items reopened and closed again count on the later date.
In the Jira help:
The Resolution timestamp is automatically updated when there is an update to the Resolution field.
How to Capture the Initial Resolution Date | Jira and Jira Service Management | Atlassian Support, read 2026-11-12.A clean-up that gives older closed items a resolution can land many resolutions on one day.
In the Jira help:
Existing issues in Resolved or Closed that have no resolution can be fixed by reopening and re-closing with a resolution.
Resolved issues appearing in Open issues filters | Jira and Jira Service Management | Atlassian Support, read 2026-11-12.If reopening an item does not clear its resolution, it can still be counted as resolved while work on it carries on.
In the Jira help:
That means some Jira gadgets will treat these issues as Resolved even if they are under a To Do or In Progress status.
Clear the resolution field when an issue is reopened in Jira Cloud | Jira and Jira Service Management | Atlassian Support, read 2026-11-12.If the resolution field is on a screen people use to edit items, an ordinary edit can set a resolution.
In the Jira help:
A resolution was added to a screen, which was then used to edit the issue.
Edit resolutions in closed Jira issues | Jira and Jira Service Management | Atlassian Support, read 2026-11-12.
How do I check it myself?
Open a few of the items in the jump and look at their history to see when each was first resolved.
In the Jira help:
The only way to see when this was first resolved is by accessing the history tab in your issue.
How to Capture the Initial Resolution Date | Jira and Jira Service Management | Atlassian Support, read 2026-11-12.Check whether the items counted have a resolution set, since Jira treats any item with one as resolved, whatever its status.
In the Jira help:
Jira considers issues with a resolution set as "Resolved issues."
Clear the resolution field when an issue is reopened in Jira Cloud | Jira and Jira Service Management | Atlassian Support, read 2026-11-12.
How does Jira work with Feder?
- Connect Jira to Feder and it joins your Wins apps.
- 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.
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.
See whether you can trust the numbers in Jira, one of your Wins apps. Feder only reads. It never changes anything in Jira.
What else goes wrong with these numbers?
- Why are finished work items missing from my Jira reports?Jira
- Why did the completed points for a past Jira sprint change?Jira
- Why did Google Analytics stop collecting data?Google Analytics
- Why aren't my key events showing in Google Analytics?Google Analytics
- Why does Google Analytics show (not set)?Google Analytics
See every question.
Where do these answers come from?
Every cause and check on this page comes from the Jira help 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.