You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Created by: Ben Parizek ([email protected]) on 2015/03/12 23:19:32 +0000
Votes at time of UserVoice import: 6
In many cases we have had the need for a Date Range field. A field that has two dates, side by side, where each field knows a little bit about the other when the user makes a selection.
While plugins can add support for this on their own, the pattern is common enough across various use cases that users would benefit from having a consistent UI, and so that Calendar plugins, Event plugins, Product plugins, Reporting plugins, and possibly even native Element search could use a standardized date range field allowing users to add content with date ranges and select data within date ranges easily.
This discussion was converted from issue #1004 on July 13, 2021 03:55.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In many cases we have had the need for a Date Range field. A field that has two dates, side by side, where each field knows a little bit about the other when the user makes a selection.
While plugins can add support for this on their own, the pattern is common enough across various use cases that users would benefit from having a consistent UI, and so that Calendar plugins, Event plugins, Product plugins, Reporting plugins, and possibly even native Element search could use a standardized date range field allowing users to add content with date ranges and select data within date ranges easily.
Beta Was this translation helpful? Give feedback.
All reactions