#81 — Difference between iteration start/end date of None or really today not visible

StateResolved
Version:
AreaUser interface
Issue typeFeature
SeverityMedium
Submitted byMaurits van Rees
Submitted onSep 23, 2008
Responsible Reinout van Rees
Target release: 2.0
Return to tracker
Last modified on Jan 08, 2009 by Matthew Wilkes
Since a while Iterations get the current date as start date by default. Old iterations may not have a start date yet (they may be iterations that are not yet planned in). In the UI the difference between an Iteration with no start date and one with a start date that really is today is not visible.

Mostly the same for end date: the difference between no end date and an end date of today is not visible.
Added byReinout van ReesonSep 23, 2008 10:17 AM
Issue state: unconfirmedopen
No start date: that's an error. I'll render it as a warning instead.

No end date: I'll render it as a text "no end date selected yet".
Added byReinout van ReesonSep 23, 2008 11:49 AM
Issue state: openresolved
Added checks whether start/endDate are set as toLocalizedTime(None) returns today as value. So unset start/end dates looked like today.

No responses can be added.