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

[Feature Request]: Request for a DatetimeRange component with time selection & other common options #17370

Open
2 tasks done
anjana-tomy opened this issue Sep 6, 2024 · 1 comment
Labels
proposal: open This request has gone through triaging. We're determining whether we take this on or not.

Comments

@anjana-tomy
Copy link

anjana-tomy commented Sep 6, 2024

The problem

The current daterange picker supports only date selection, there is no option to filter based on time or easy chose option like current week, today, current month etc
Screenshot 2024-09-06 at 12 41 28 PM
Screenshot 2024-09-06 at 1 03 42 PM

The solution

There should be an option to select between a certain time range as well.
The user should be able to easily common ranges like today, past 24 hrs, yesterday, last week, last month etc

The normal illustrations image are attached
Screenshot 2024-09-06 at 1 03 42 PM
Screenshot 2024-09-06 at 12 41 28 PM

Design link

Current existing carbon component
https://carbondesignsystem.com/components/date-picker/usage/
https://react.carbondesignsystem.com/?path=/story/components-timepicker--default

Example to requested enhancement
https://hypeserver.github.io/react-date-range/

Links to other materials

No response

Owner/main maintainer(s)

[email protected]

Second/backup maintainer(s)

No response

Product/offering

Ikigai under software defined networking

Business priority

Medium Priority = upcoming release but is not pressing

Code of Conduct

@ljcarot ljcarot transferred this issue from carbon-design-system/ibm-products Sep 6, 2024
@ljcarot ljcarot moved this to 🕵️‍♀️ Triage in Design System Sep 6, 2024
@alisonjoseph alisonjoseph added proposal: open This request has gone through triaging. We're determining whether we take this on or not. and removed status: needs triage 🕵️‍♀️ labels Sep 11, 2024
@JordanWSmith15
Copy link

@sstrubberg The Sustainability Apps BU has created a version of this in our storybook. We have many scenarios where it is required; we have legacy applications that have database objects combining date and time range data into a single attribute. Validation is run as a whole rather than individually against the application's business rules. Because of this, using 4 separate Carbon inputs to manage date, time, start and end is not a good UX for error handling.
We have had challenges upgrading this custom component from Carbon V10 to V11. Please consider prioritizing this enhancement in the future.
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal: open This request has gone through triaging. We're determining whether we take this on or not.
Projects
Status: 🕵️‍♀️ Triage
Development

No branches or pull requests

3 participants