Content
View differences
Updated by Parimal Satyal about 3 years ago
The date picker for work packages were updated in versions 12.2 and 12.3. There are however other views in OpenProject where date pickers exist and that are currently implemented differently than on work packages.
This feature seeks to list all of these different views, and propose a standardised "date-only" date picker that looks and behaves the same as the date picker for work packages.
### Identified views
* **Work package and project custom fields**
* **Single non-working days**
**(Update 15.02.2023)**
These views will now NOT use this simple drop-modal date picker. Instead, they use the basic drop-down datepicker, described in: ###46236
* **Log time** (from work package, from My Saved view, when editing previously logged time)
* **Log unit cost** (from work package, when editing previously logged unit cost)
* **Meeting minutes**
* **Work package table filters**
* **Work package bulk edit form**
* **Announcement edit form**
* **Version new & edit form + custom fields**
* **Project filters**
* **Cost report filters**
* **Cost report filters**
* **Budget forms**
* **Dynamic forms**
* **Pause date reminders**
* **Work package and project custom fields**
### Date-only picker
The date-only picker is a variation of the date picker for work packages (described in <mention class="mention" data-id="42047" data-type="work_package" data-text="#42047">#42047</mention>):
* It behaves like a drop modal.
* In mobile, the drop modal takes the full-screen (and effectively behaves as a normal modal). This can cause double-layering in some cases; this is acceptable.
* It doesn't have the scheduling or banner bits.
* It is otherwise the same as the simple date picker used in mobile.
* There is the option to add additional input fields on top of the date if needed, for example:
* Text fields
* Repeated date field (if the item calling the date picker isn't an input field)
* The toggle of "Working days only" is not enabled by default but can be added where relevant.
* For 12.5, they will only be enabled in these places:
* ~~Log time~~
* ~~Log unit cost~~
* Work package and project custom date fields
* ~~Announcement edit form~~
* ~~Cost report filter~~
* ~~Budget forms~~
* ~~Meeting forms~~
* When the toggle is displayed, it is _ON_ by default.
* The text for primary button in the action bar is configurable:
* **By default, it is "Apply"** (where the action then requires a save action later)
* Log time
* Log unit costs
* Meeting minutes
* Pause date reminders
* Work package table filters
* Work package bulk edit form
* Announcement edit form
* Version new & edit form + custom fields
* Project filters
* Cost report filters
* Cost report filters
* Budget forms
* Dynamic forms
* **In the following places, it is "Add"** (where the action adds the date to a list)
* Single non-working days
* **In the following places, it is "Save"** (where the action saves the data immediately)
* Work package and project custom fields (type date)
* Milestones
* Backlog edit
* The logic and behaviour follows the current implementation in <mention class="mention" data-id="42047" data-type="work_package" data-text="#42047">#42047</mention>.
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/49874/content">
### Out of scope
* The fact that the currently used date picker (the default Flatpickr one), has week numbers whereas the "new" OP one does not. Some clients have requested this to be reinstated; this is being tracked in <mention class="mention" data-id="35329" data-type="work_package" data-text="#35329">#35329</mention>.
This feature seeks to list all of these different views, and propose a standardised "date-only" date picker that looks and behaves the same as the date picker for work packages.
### Identified views
*
*
**(Update 15.02.2023)**
These views will now NOT use this simple drop-modal date picker. Instead, they use the basic drop-down datepicker, described in: ###46236
* **Log time** (from work package, from My Saved view, when editing previously logged time)
* **Log unit cost** (from work package, when editing previously logged unit cost)
* **Meeting minutes**
* **Work package table filters**
* **Work package bulk edit form**
* **Announcement edit form**
* **Version new & edit form + custom fields**
* **Project filters**
* **Cost report filters**
* **Cost report filters**
* **Budget forms**
* **Dynamic forms**
* **Pause date reminders**
* **Work package and project custom fields**
### Date-only picker
The date-only picker is a variation of the date picker for work packages (described in <mention class="mention" data-id="42047" data-type="work_package" data-text="#42047">#42047</mention>):
* It behaves like a drop modal.
* In mobile, the drop modal takes the full-screen (and effectively behaves as a normal modal). This can cause double-layering in some cases; this is acceptable.
* It doesn't have the scheduling or banner bits.
* It is otherwise the same as the simple date picker used in mobile.
* There is the option to add additional input fields on top of the date if needed, for example:
* Text fields
* Repeated date field (if the item calling the date picker isn't an input field)
* The toggle of "Working days only" is not enabled by default but can be added where relevant.
* For 12.5, they will only be enabled in these places:
* ~~Log time~~
* ~~Log unit cost~~
* Work package and project custom date fields
* ~~Announcement edit form~~
* ~~Cost report filter~~
* ~~Budget forms~~
* ~~Meeting forms~~
* When the toggle is displayed, it is _ON_ by default.
* The text for primary button in the action bar is configurable:
* **By default, it is "Apply"** (where the action then requires a save action later)
* Log time
* Log unit costs
* Meeting minutes
* Pause date reminders
* Work package table filters
* Work package bulk edit form
* Announcement edit form
* Version new & edit form + custom fields
* Project filters
* Cost report filters
* Cost report filters
* Budget forms
* Dynamic forms
* **In the following places, it is "Add"** (where the action adds the date to a list)
* Single non-working days
* **In the following places, it is "Save"** (where the action saves the data immediately)
* Work package and project custom fields (type date)
* Milestones
* Backlog edit
* The logic and behaviour follows the current implementation in <mention class="mention" data-id="42047" data-type="work_package" data-text="#42047">#42047</mention>.
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/49874/content">
### Out of scope
* The fact that the currently used date picker (the default Flatpickr one), has week numbers whereas the "new" OP one does not. Some clients have requested this to be reinstated; this is being tracked in <mention class="mention" data-id="35329" data-type="work_package" data-text="#35329">#35329</mention>.