Reports - Release Burndown
I know this problem/bug was reported years back, but Im seeing this behavior and I wish there was a way to fix it?! I've assigned a Fix Version release number (EET- H1-2025) across numerous epics and using the Release Burndown report to visualize and track progress. What I'm seeing in the report though is a bunch of additional sprints that aren't part of the Releases' Start Date (see attached image).
How can I clean this up so that these additional sprints are removed? I believe it's messing up the estimations and reporting of how many sprint remain to complete this work based on my teams velocity of "20 points per sprint", which doesnt make sense.
I've looked into whether I have multiple Fix Version numbers assigned within tickets from past sprints and releases, but Im not seeing that.
Thoughts? I appreciate your feedback. Thanks!
1 answer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.