Patricia Carrasco (pcar)2018-02-07 14:23 Hi, it should be consistent with burndown. For my sprint tracker, I'm displaying the burnup and burndown. Thanks
Thomas Gorka (tgorka)2018-02-07 14:14 Hi, Your sprint lasts 10 working days but the global duration including week-ends worth approximately 15 days (enough to switch the display in weeks). However, I agree to say the script should not take weekends into account to deduce the right time frame to use and that it has to be fixed.
Patricia Carrasco (pcar)2018-02-07 13:34 Hi Thomas, as per your definition below, my sprint is two weeks (10day) but it is displaying the time scale in weeks. Attachments burnup_date_issue.png addedBy Patricia Carrasco (pcar)(22 kB)burnup_date_issue.pngBurnup time scale issue
Thomas Gorka (tgorka)2018-02-07 08:51 Hello, The granularity of the time scale is set up accordingly to the duration of the sprint. As of today, the thresholds are respectively: • From 2 days to 2 weeks -> Dates are displayed as usual. • From 2 weeks to 3 months -> Weeks are displayed • More than 3 months -> Months are displayed. We can increase the limit for dates, but we have to stay reasonable or the X axis will become barely readable because label will overlap themselves. I propose the following solution: From 2 days to 3 weeks -> Dates are displayed as usual. This way, dates are displayed for sprints lasting up to 15 days, but it is the very limit. Please find in attachment two screen-shots illustrating my explanations. What do you think about that? Attachments labels_overlaping.png, burnup_sprint_10_days_ok.png addedBy Thomas Gorka (tgorka)(18 kB)labels_overlaping.pngBy Thomas Gorka (tgorka)(16 kB)burnup_sprint_10_days_ok.png