Rally: Why dates are inconsistent in Release & Iteration burndown app
search cancel

Rally: Why dates are inconsistent in Release & Iteration burndown app

book

Article ID: 278373

calendar_today

Updated On:

Products

Rally SaaS

Issue/Introduction

We have identified an issue in the burndown chart where the dates on the X-Axis appear to be randomly assigned for teams within the same PI. Ideally, these dates should represent either the start or end of an iteration. We require the consent of the Broadcom team to address this issue

Environment

Rally SAAS

Cause

Release & Iteration burndown app is working as designed.

 

Resolution

The dates in the chat are automatically generated by the Release & Iteration burndown app, based on the start and end dates of each Release. It’s important to note that each Release has a unique duration, hence the app algorithm adjusts the dates accordingly. This means that the dates may not be identical across all teams. This approach ensures that the data accurately reflects the specific timeline of each team’s Release.


Sample taken when the Release period is set for 1 month between (01/01/24 -- 01/31/24)

 

Sample taken when the Release period is set for 2 weeks between (01/15/24 -- 01/26/24)