-
Suggestion
-
Resolution: Fixed
-
None
- Default on new boards is not to show sat / sunday in the timezone of the server
- Affects burndown chart only (and mini burndown in sprint report)
- Default to timezone of server but allow to be changed
- Display timezone being used
- New reports tab in configuration
- Allow additional days to be specified
- If JIRA has a weekend setting use that for the default (rather than just Sat/Sun)
Development Notes
Q: Must test when there is a switch-over from standard time to daylight savings.
A: Not Tested
Q: What if the non-working days are not valid?
A: Not Answered
Q: What if all days are marked as non-working days?
A: Not Tested
Q: What if the sprint starts or ends on a non-working day?
A: Not Tested
Q: Is there support for defining which days are your weekend? aka the Saudi case
A: Not Answered
Q: Is the chart displayed in the client's timezone, the user's timezone (from profile), or server? Chart should line up with the sprint dates.
A: Not Answered
Q: What if there are datapoints in a non-working day time period (shaded area)? Are they treated the same or excluded?
A: Not Tested
Q: What if 2 non-working periods overlap?
A: Not Answered
Q: Do any of these questions surprise you? If so, what hadn't you previously considered?
A: Not Answered
- is related to
-
JSWCLOUD-5117 Greenhopper non-working days are ignored in Rapid Views
- Closed
-
JSWCLOUD-3873 As a user, I would like the Cumulative Flow Diagram (CFD) to respect non-working days
- Gathering Interest