[MGNLPN-180] Move end date when user changes start date Created: 18/Jun/14 Updated: 11/Mar/21 Resolved: 11/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | Traits |
| Affects Version/s: | 1.0 |
| Fix Version/s: | 1.1.x |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | usability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Description |
|
Usability improvement for date trait: move end date automatically so it falls after the start date. This is common behavior in date range controls. The lack of it starts to bother after extensive use. Example: Assume you have date range Jan 1 to Jan 5. When the user moves the start date to Jan 6, the system should automatically move the end date to Jan 7. Otherwise the range is invalid. |