Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Reports - Release Burndown

Brian Ruscio
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 25, 2025 edited

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'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!

Screenshot 2025-02-25 at 8.44.28 AM.png  

1 answer

0 votes
Brian Ruscio
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 25, 2025 edited

EET H1-2025

Planned start date: 28/Jan/25 (Sprint 138)
Planned release date: 30/Jun/25

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
atlassian, atlassian community, university, on demand, transition to jira cloud

Transition to Jira Cloud

Switch to Jira Cloud with Atlassian University! Explore new navigation, issue views, and Cloud features like team-managed projects and automation. Tailored for Data Center users & admins, these courses ensure a smooth transition. Start your journey today!

Enroll now
AUG Leaders

Upcoming Jira Events