Content
View differences
Updated by Parimal Satyal about 3 years ago
### Context
This feature will explore single-date mode for work packages that _could_ take a range. The goal is to be able to:
* Specify just a finish date or just a start date
* It should be possible to add the other date at any time and turn it into a range
* It should be possible to derive the other date when duration is known (but keep it as a derived value and not an input value)
* When there are preceeds/follows relationships, changes to the derived date should also affect the dates of related work packages
**For the moment, this feature is a work in progress that still requires further discussion to clarify user needs/feature requirements.**
The actual bug report is below, and is related to related to ###45100.
###
### Mockup
Figma link: [https://www.figma.com/file/amVGcHqRQyR8x4EsqV9H99/Date-picker?node-id=261-26140](https://www.figma.com/file/amVGcHqRQyR8x4EsqV9H99/Date-picker?node-id=261-26140)
### Original bug report (archived 14.04.2023)
> ##### Steps to reproduce
>
> 1. Create a work package with only a finish date
> 2. Open the date picker
> 3. Tab to the finish date so this is active
> 4. Change a date in the mini calendar
>
> ##### What is the buggy behavior?
>
> * Not the active field (finish date) is changed. The first click changes the start date.
>
> #### <img class="op-uc-image op-uc-image_inline" style="width:595px;" src="/api/v3/attachments/54524/content">
>
> ##### What is the expected behavior?
>
> 1. Clicking in the mini calendar changes the date of the active date field (similar to Google flights)
>
> ### <img class="op-uc-image op-uc-image_inline" style="width:581px;" src="/api/v3/attachments/54523/content">
This feature will explore single-date mode for work packages that _could_ take a range. The goal is to be able to:
* Specify just a finish date or just a start date
* It should be possible to add the other date at any time and turn it into a range
* It should be possible to derive the other date when duration is known (but keep it as a derived value and not an input value)
* When there are preceeds/follows relationships, changes to the derived date should also affect the dates of related work packages
**For the moment, this feature is a work in progress that still requires further discussion to clarify user needs/feature requirements.**
The actual bug report is below, and is related to related to ###45100.
###
### Mockup
Figma link: [https://www.figma.com/file/amVGcHqRQyR8x4EsqV9H99/Date-picker?node-id=261-26140](https://www.figma.com/file/amVGcHqRQyR8x4EsqV9H99/Date-picker?node-id=261-26140)
### Original bug report (archived 14.04.2023)
> ##### Steps to reproduce
>
> 1. Create a work package with only a finish date
> 2. Open the date picker
> 3. Tab to the finish date so this is active
> 4. Change a date in the mini calendar
>
> ##### What is the buggy behavior?
>
> * Not the active field (finish date) is changed. The first click changes the start date.
>
> #### <img class="op-uc-image op-uc-image_inline" style="width:595px;" src="/api/v3/attachments/54524/content">
>
> ##### What is the expected behavior?
>
> 1. Clicking in the mini calendar changes the date of the active date field (similar to Google flights)
>
> ### <img class="op-uc-image op-uc-image_inline" style="width:581px;" src="/api/v3/attachments/54523/content">