The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Yegor Schustik
May 27, 2024

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Trudy P Claspill
Community Champion
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 P Claspill
Community Champion
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.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events