Can't see issues from closed sprint in Issue navigator with filter

Yegor Schustik May 27, 2024

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 27, 2024

Hello @Yegor Schustik 

Welcome to the Atlassian community!

I have not been able to replicate your scenario so far. I do see that you are using a Team Managed Software project, and I made sure to do the same when trying to replicate your error.

How do you know that there are issues in that sprint?

Can you show us the Sprint Burndown for that sprint to show us that there are issues in it?

Yegor Schustik June 5, 2024

Here the report https://tppr.me/cxL0x 

Yegor Schustik June 5, 2024

Thanks for your reply I see that it is a bug )

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 5, 2024

I see that the sprint name you have specified in your filter does not match the sprint name shown on the burndown report.

The name in the filter has a "p" in it.

Screenshot 2024-06-05 at 7.04.08 AM.png

The name in the chart does not.

Screenshot 2024-06-05 at 7.04.20 AM.png

So your filter is not actually trying to retrieve issues for the sprint you are looking at in the Burndown Chart.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events