Be able to calculate end date based on duration

[Bastien Delourmel]

Good afternoon,

WE ARE USING BIGPICTURE

What I want: when the schedulers set a start date and a duration in the ticket, the end date is automatically calculated. The end date MUST adapt itself regarding: 

• Non-working day (or company holiday)

For exemple, if the start date is Monday 21 february and the duration equal 3 days, then the end date will be Thursday 24 february. BUT, if the wednesday 23 february is a non-working day (or company holiday), then the end date MUST be set to 25 friday february. 

Is there an automation for that?

Thanks a lot for your help! :)

[Anna-BigPicture · Accepted solution]

Hi @Bastien Delourmel ,

The answer is: Yes and Yes.

BigPicture gives the possibility of auto-scheduling based on task duration. I explained the scheduling mechanism in my article: BigPicture tutorial - Dates synchronization. I hope you find it useful!

Please bear in mind that the first and crucial step is correct fields mapping, which is explained in our wiki: Tasks.

And the last thing, whenever you want those non-working days or assignee absences were taken into account, simply enable this option in App Configuration. See my image as a reference.

[Bastien Delourmel]

Good afternoon, 

Thanks a lot for your answer :-) 

It does work, but I still have an issue: 

If we add a Start Date (21.02.22) + an Original Estimate (3d), the ticket will show the end date as : 23.02.22.

THEN, we add our non-working day for the 22.02.22 on our Holiday plan → The end date won't be updated automatically. This approach won't take into consideration the non-working day.

Is there a way to update the end date after adding the start date + original estimate? :)

Thanks, 

Regards,

[Bastien Delourmel]

@Anna-BigPicture up :)

thanks :)

[Anna-BigPicture]

Hi @Bastien Delourmel

If working days are changed (globally or for individual resource), it has no immediate effect on scheduling. The changes in working days are only considered if scheduling is triggered on the affected tasks by some other action. Some changes, e.g., adding a long absence or changing global working days, might have a massive impact on scheduling that the user won't be able to anticipate.
 
However, we are going to implement a new mechanism, which in case of changes that will affect working days, will dry run of scheduling to estimate the impact of the changes made, and If the user accepts the changes are automatically applied to all affected tasks.