Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DatePicker improvements #2960

Open
1 task
danielskovli opened this issue Jan 31, 2025 · 0 comments
Open
1 task

DatePicker improvements #2960

danielskovli opened this issue Jan 31, 2025 · 0 comments
Labels
kind/user-story Used for issues that describes functionality for our users. status/draft Status: When you create an issue before you have enough info to properly describe the issue. status/triage

Comments

@danielskovli
Copy link
Contributor

danielskovli commented Jan 31, 2025

Description

As a user of a form that has a start and end date, I would like the end date to default to the view of the start, so I can more easily pick dates far in the future.

Additional Information

Linking two or more DatePicker components would make the user experience when picking related dates smoother. For instance, if picking a start date a year in the future, you have to click a handful of times to get that far. Then you move on to the end date component, which defaults to today's date and you have to perform the exact same clickathon again.

Not only is this cumbersome, it increases the risk of incorrect data being entered by the user.

Acceptance Criterias

  • Defaulting a DatePicker's view to the value of another DatePicker's selected value should be possible. Note that the DatePicker value itself should not be automatically set to anything, just that the selection view should be navigated to the right day/month/year/milliennia
@danielskovli danielskovli added kind/user-story Used for issues that describes functionality for our users. status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/user-story Used for issues that describes functionality for our users. status/draft Status: When you create an issue before you have enough info to properly describe the issue. status/triage
Projects
Status: No status
Development

No branches or pull requests

1 participant