Spike Smart Duration + Sequential Due Date Issue with Due Dates going to the past or going out of order
When a user completes a step on a Task made using a template, the Step Due Date is updating to a past date. This is causing the cascading update to Smart Duration. The original issue was thought to be that the Smart Duration is working as expected. But its really the first date being on a wrong date that is causing the whole problem. On the screenshot attached, notice how an action taken on June 12 is making the Due Date shift to June 9th automatically. Which should not happen.
- Due Dates should not update just because of completion of a step.
- Due Dates should not update to the past date.
- Due Dates can be out of sequence (so the logic of sequential should only remain for incomplete steps, not for completed ones).
13
votes