-
Notifications
You must be signed in to change notification settings - Fork 139
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
[Enhancement request]: Change date picker on custom field #894
Comments
@Bhavyajain21 I would like you to work on this when you are done with your current issue. Lets discuss it. |
Sure @DonKoko |
Let's implement the similar Date field - as what we currently have under the Bookings? @DonKoko |
@Bhavyajain21 yes, it needs to be just a normal html date input, the same as with bookings but without the time. That means we dont need the popover or anything like this as that comes native in the browser. /bounty 10 |
|
/attempt
|
💡 @Bhavyajain21 submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
🎉🎈 @Bhavyajain21 has been awarded $10! 🎈🎊 |
@carlosvirreira this has been adjusted and released to live. We replaced the date picker with had with a native browser date picker which works smoother on all devices. We also included the button to clear it for the case when its a not required field and the user might want to do that. Would be great if you can inform the users that asked for it. |
Doing right now and will be part of the small improvement notes on an upcoming Newsletter. |
Contact Details
No response
Is your feature request related to a problem? Please describe?
I sometimes spend too much time clicking around with the current date modal for custom fields (date) to select the purchase date of my assets.
Some of my assets are 10 years old. Lots of clicking around.
Describe the solution you'd like
Can we use a date picker similar to the one we have in Bookings? Without the time field. Just date. Or just let me input a date in text.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: