Bug #5495
closed
Date dropdowns can not have a minimum date without a maximum date and vise verse
Added by krileon about 9 years ago.
Updated almost 8 years ago.
Start date:
02 September 2015
Description
When specifying a minimum date for a calendar dropdown usage a maximum date also must be specified. It should be allowed to function independently then offset from the one date supplied as needed.
- Target version changed from CB 2.0.11 to CB 2.0.12
- Target version changed from CB 2.0.12 to CB 2.0.13
- Target version changed from CB 2.0.13 to CB 2.0.14
- Target version changed from CB 2.0.14 to CB 2.0.15
- Target version changed from CB 2.0.15 to CB 2.1
To clarify further. If you want a single year you can't. For example set minimum year to 2016 then maximum year to +0 and you get 2016 and 2017 years. This is due to the hardcoded +1 year, which really should not be there unless the parameter is completely empty. Specifying the same year or +0 should never pad by +1.
If minimum year is greater than maximum year it should just flip them. Instead it's currently subtracting 1000 years from minimum which doesn't make any sense and potentially can cause some significantly invalid ranges.
Fixed in MR !1189
Empty, current year (e.g. 2016), or +0 can all be used to always be the current year. This avoids the forced +1 to maximum year when using current year. If minimum year is greater than maximum year it'll reverse the two to make sense (the range is still 100% valid for what they supplied).
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by