#81 — Difference between iteration start/end date of None or really today not visible
by
Maurits van Rees
—
last modified
Jan 08, 2009 02:57 PM
| State | Resolved |
|---|---|
| Version: |
—
|
| Area | User interface |
| Issue type | Feature |
| Severity | Medium |
| Submitted by | Maurits van Rees |
| Submitted on | Sep 23, 2008 |
| Responsible | Reinout van Rees |
| Target release: | 2.0 |
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.
Mostly the same for end date: the difference between no end date and an end date of today is not visible.
Added by
Reinout van Rees
on
Sep 23, 2008 10:17 AM
No start date: that's an error. I'll render it as a warning instead.
Issue state:
unconfirmed
→
open
No end date: I'll render it as a text "no end date selected yet".
Added by
Reinout van Rees
on
Sep 23, 2008 11:49 AM
Added checks whether start/endDate are set as toLocalizedTime(None) returns today as value. So unset start/end dates looked like today.
Issue state:
open
→
resolved
No responses can be added.
If you can, please log in before submitting a reaction.