-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Improve custom date range selector #2779
Comments
+1 |
Note that changing the time bucketing (e.g. hourly) often resets the date range selected, leading to even more clicks. |
This issue hasn't seen activity in 6 months. Is it still relevant? |
Think this is still quite relevant. Tagging @clarkus for ideas here |
Still relevant (#5173 (comment)) as it relates to session filters. #2990 as well. I have some ideas for this. I'll add it into my design queue 👍 |
Here is a basic pattern for a datepicker that is optimized for ranges. This is a bit separate from the input that would summarize the selected values. I am working on something for that now. Important aspects to the picker below:
|
I did some research looking for react-based datepicker components we could use for this need. https://github.com/airbnb/react-dates looks fairly complete. The one thing I didn't find support for was quickly navigating years. |
This issue hasn't seen activity in two years! If you want to keep it open, post a comment or remove the |
This issue was closed due to lack of activity. Feel free to reopen if it's still relevant. |
Is your feature request related to a problem?
Experience with the custom date range selector (see below) is a bit clunky. You need a ton of extra clicks to navigate around.
Describe the solution you'd like
Have something like Airbnb or your typical airline where the range selector opens automatically and then it lets you select a range more easily (without having to select a start date and and an end date individually).
Describe alternatives you've considered
Keep the current experience.
Additional context
Came from customer call.
Thank you for your feature request – we love each and every one!
The text was updated successfully, but these errors were encountered: