Content
View differences
Updated by Jens Ulferts 12 months ago
### Steps to reproduce
1. Have 2 phases (A, B) with dates set
2. Clear phase A finish date
3. Clear phase B start date
4. On Set phase A, set A the finish whole date range to an
1. **earlier date** than phase B's B finish date. date set in step #2.
2. **later **latter date** than phase B's B finish date. date set in step #2.
5. Open the Phase B edit dialog. It will display the default start date and the finish date, but the start date field is not yet set, so it will not appear as completely set.
6. Clicking save on phase B without any modifications will either:
1. set the range correctly. (If 4.a is chosen)
2. display an error message on the disabled start date. (If 4.b is chosen)
### What is the buggy behavior?
* In case **4.a** the range appears to be complete on **phase B**, however the start date is not yet stored and we display the default start date only.
* In case **4.b** the same issue as 4.a on **phase B**, plus it will display a validation error message on the start date being later than the finish date.
### What is the expected behavior?
1. \[OPEN\] In case **4.a:**
1. Set **4.a** not sure, maybe set the start date of phase B to during the next working day reschedule happening after the finish date of saving phase A.
2. The duration is updated accordingly (finish date - start date of B).
3. The values are stored in the database.
2. \[OPEN\] In case **4.b:**
1. Set **4.b** display the start date of B to error message on the next working day after the finish date of A
2. Set date, because the finish start date of B to the next working day after the finish date of A.
3. The duration is not editable. But since we set to 1.
4. The values are stored in the database.
3. In case 4.a/4.b are done not with the finish date on A but with the start date only, the behaviour should be just the same. Meaning if only the start date of phase A is set and not the finish date, it automatically, we will have create an affect on invalid phase, so not sure what would be the dates of B. right solution here.
The behaviour should by that be identical to how scheduling happens for work packages.
<br>
### Screenshots and other files
1. **Setting earlier dates on Phase A than Phase B finish date.**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/649692/content">
2. **Setting latter dates on Phase A than Phase B finish date.**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/649694/content">
###
1. Have 2 phases (A, B) with dates set
2. Clear phase A finish date
3. Clear phase B start date
4. On
1. **earlier date** than phase B's
2. **later
5. Open the Phase B edit dialog. It will display the default start date and the finish date, but the start date field is not yet set, so it will not appear as completely set.
6. Clicking save on phase B without any modifications will either:
1. set the range correctly. (If 4.a is chosen)
2. display an error message on the disabled start date. (If 4.b is chosen)
### What is the buggy behavior?
* In case **4.a** the range appears to be complete on **phase B**, however the start date is not yet stored and we display the default start date only.
* In case **4.b** the same issue as 4.a on **phase B**, plus it will display a validation error message on the start date being later than the finish date.
### What is the expected behavior?
1.
1. Set
3. The values are stored in the database.
2.
1. Set
2. Set
3. The duration is
4. The values are stored in the database.
3. In case 4.a/4.b are done not with the finish date on A but with the start date only, the behaviour should be just the same. Meaning if only the start date of phase A is set and not the finish date, it
The behaviour should by that be identical to how scheduling happens for work packages.
<br>
### Screenshots and other files
1. **Setting earlier dates on Phase A than Phase B finish date.**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/649692/content">
2. **Setting latter dates on Phase A than Phase B finish date.**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/649694/content">
###