Project Summary missing issues

[Beth Jokhio]

I had created a new Team Managed Software project and told management about the Project Summary page, which they have been using multiple times a day to generate reports on progress.

Earlier this week, I noticed that the count of issues on the Summary donut was not matching the actual count of issues (that is the 'Summary Donut' count vs 'All Items' count didn't match).  I found it was easy to determine which issues were missing by using the 'View all work items' link above the Summary Donut which takes you to a filtered list view; scrolling down the list so that all issues load, and then use the select all checkbox.  Then clear the filter and the selected issues persist highlighted while the additional items are not selected so it's easy to see (if not count) the items that were missing. 

I see no reason these items were excluded.  They are all 'Done', but not archived.  Some of the excluded tickets were active in the last 7 days, while others that were included were active >7 days ago.  (I mention this as I saw in other comments that the summary limits itself to the previous 7 days, but if a project summary excludes items over 7 days old, that's a poor indicator of actual project progress)

Anyone else experience this, or is this working as intended and I just don't understand how the summary page works?  I can't find any information online as to what filter is used to generate the Summary Donut.

[Gor Greyan]

Hi @Beth Jokhio

Welcome to the Atlassian Community!

The “Summary” donut chart on a Team-Managed Jira project does not show a full count of all issues.
Atlassian’s documentation confirms that it only includes items updated recently:

• Only “Done” issues completed in the last 2 weeks appear in the Summary Donut (or “Status Overview”).

• Older Done items (beyond 14 days) are automatically excluded, even though they are still visible in “All Work Items.”

• This is intended behavior, not a bug — the Summary view is designed as a recent activity snapshot, not a full historical report.

There is also an option to show these ranges: 

[Beth Jokhio]

Thanks for the response, @Gor Greyan 
Where do you find the setting to change the date range? 

[Gor Greyan]

You can find it by clicking the three dots next to the Done column. You will see "Remove Done Items after X days". Enter there, you can change it.

[Beth Jokhio]

Ah, thanks for your response.  It's a Scrum project, and the board being Sprint-based doesn't have that option, as far as I can tell.

[Beth Jokhio]

I still have questions about why certain items were excluded. 
Following the steps I detailed above, the selected items in this screenshot were included in the Summary Donut, while the unselected items were not.
Today is October 17.  If dates are doing the filtering, why is TTU-60 included in the filter while TTU-127 was not?

[Gor Greyan]

@Beth Jokhio

Both TTU-60 and TTU-127 are in a green (Done category) status.
However, Jira’s Summary Donut only includes issues that entered the Done category within the configured retention period (14 days by default). I think,
TTU-127 was completed before that threshold, so it’s automatically excluded even though its status is still green.
If you extend the Done retention to 30 or 60 days, it will show up again.

[Beth Jokhio]

Thanks again, but any idea how to do that on a Scrum board?  Those 3 dots don't show up there  (even on hover).

[Gor Greyan]

Hi @Beth Jokhio

In Team-Managed Jira projects, the “Remove done items after X days” option currently applies only to Kanban boards, not Scrum boards — which is why you don’t see the three-dot menu on your “Done” column in Scrum. In Scrum, Jira’s cleanup logic isn’t “remove after X days,” but rather “remove when the sprint is completed.”