# Project Duration **URL:** \ **Category:** Get Help\ **Created:** [April 24, 2025, 4:00pm UTC](https://community.fibery.io/t/project-duration/8661 "2025-04-24T16:00:53Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![fewlo](https://avatars.discourse-cdn.com/v4/letter/f/7bcc69/32.png) [@fewlo](https://community.fibery.io/u/fewlo)\ **Post date:** [April 24, 2025, 4:00pm UTC](https://community.fibery.io/t/project-duration/8661/1 "2025-04-24T16:00:53Z")
Hello all, I’m really new to Fibery and loving the power of it but also getting a little lost 🙂 so need help please. I create potential Projects with an estimated duration so we can see our year ahead using a Timeline view. When one of these projects goes ‘live’ I then add numerous tasks associated to the project with a more detailed breakdown of duration. Is there a way to update the Project duration by getting the earliest start date and latest end date from these associated tasks, then have this as a link that automatically updates as tasks move? Thank You, Michael. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [April 24, 2025, 4:15pm UTC](https://community.fibery.io/t/project-duration/8661/2 "2025-04-24T16:15:05Z")
> [@fewlo](#): > > Is there a way to update the Project duration by getting the earliest start date and latest end date from these associated tasks Yes, with an automation rule (when the Project gains a Task, update the Project duration). > [@fewlo](#): > > then have this as a link that automatically updates as tasks move? Again, with an automation rule (when the Task date is updated, update the parent Project’s date range) ---
**Author:** ![fewlo](https://avatars.discourse-cdn.com/v4/letter/f/7bcc69/32.png) [@fewlo](https://community.fibery.io/u/fewlo)\ **Post date:** [April 24, 2025, 8:25pm UTC](https://community.fibery.io/t/project-duration/8661/3 "2025-04-24T20:25:41Z")
Hi, thanks for answering so quick, I’ve been trying to set this up but can’t get it to work. I’ve tried; When 1. entity linked to project \> tasks Then 2. Update \> duration But nothing changes, even though in activity it suggests an update. Your instructions seemed simple and clear so I’m missing something, is a formula required in part 2? Thanks for any help, Michael. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [April 24, 2025, 9:52pm UTC](https://community.fibery.io/t/project-duration/8661/4 "2025-04-24T21:52:41Z")
> [@fewlo](#): > > Your instructions seemed simple and clear so I’m missing something, is a formula required in part 2? Sorry I wasn’t more clear. Yes, you need a formula. Something like this: `DateRange([Step 1 Project].Tasks.Min(Dates.Start()),[Step 1 Project].Tasks.Max(Dates.End()))` and for the second automation, maybe something like this: `DateRange([Step 1 Task].Project.Tasks.Min(Dates.Start()),[Step 1 Task].Project.Tasks.Max(Dates.End()))` ---
**Author:** ![fewlo](https://avatars.discourse-cdn.com/v4/letter/f/7bcc69/32.png) [@fewlo](https://community.fibery.io/u/fewlo)\ **Post date:** [April 25, 2025, 6:40am UTC](https://community.fibery.io/t/project-duration/8661/5 "2025-04-25T06:40:30Z")
Brilliant, thanks this works great! In some cases the rules cannot apply, which I understand is expected behaviour so I would like to try and avoid the following happening. Now when I move a full project in timeline view, it is not synced with any tasks associated to it. Should I now avoid moving projects in my timeline view, or can I rule be setup to move all associated tasks? Thanks, Michael. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [April 25, 2025, 8:50am UTC](https://community.fibery.io/t/project-duration/8661/6 "2025-04-25T08:50:22Z")
Imagine a Project that consists of Tasks with the following dates: Task 1 - 01/03/2025→31/03/2025 Task 2 - 18/03/2025→30/04/2025 Task 3 - 10/04/2025→29/04/2025 The Project overall dates would be 01/03/2025→30/04/2025 What do you think should happen if a user changes the overall Project dates to 15/03/2025→25/04/2025 ? > [@fewlo](#): > > Now when I move a full project in timeline view, it is not synced with any tasks associated to it. > Should I now avoid moving projects in my timeline view, or can I rule be setup to move all associated tasks? In theory, you could write an automation that updates all the Tasks within a Project when the Project dates change, but I expect you will have trouble defining what logic should be used to determine the Task dates in a way that will behave reasonably. Also, there will be a risk that you will get automation loops being triggered, i.e. adjusting the Project dates causes the Task dates to be changed, which triggers the automations which update the Project dates, and so on. Have you looked at using [dependencies](https://the.fibery.io/@public/User_Guide/Guide/Dependency-management-111) on a timeline to allow you to shift Tasks (whilst retaining the automation that updates the parent Project)? ---
**Author:** ![fewlo](https://avatars.discourse-cdn.com/v4/letter/f/7bcc69/32.png) [@fewlo](https://community.fibery.io/u/fewlo)\ **Post date:** [April 25, 2025, 8:59am UTC](https://community.fibery.io/t/project-duration/8661/7 "2025-04-25T08:59:43Z")
> [@Chr1sG](#): > > What do you think should happen if a user changes the overall Project dates to 15/03/2025→25/04/2025 ? This is slightly different from what I would do, as the overall duration has also changed in your example so I can see how this would be problematic. I use dependencies in our tasks timeline and this works great, I think going forward it is best to just use our project timeline as a report that can’t be edited, as the automations you set up for us have solved our immediate issue. Cheers for all the help @Chr1sG its much appreciated. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [April 25, 2025, 9:11am UTC](https://community.fibery.io/t/project-duration/8661/8 "2025-04-25T09:11:27Z")
Yep, that makes sense. It’s a bit naff, but you could maybe add a formula that gives a text warning if a Project has Tasks (from which it’s duration is derived). Then you can show this warning field on any relevant Project views (and choose Hide when empty). It might help users to remember not to move these Projects. ---
**Author:** ![fewlo](https://avatars.discourse-cdn.com/v4/letter/f/7bcc69/32.png) [@fewlo](https://community.fibery.io/u/fewlo)\ **Post date:** [April 25, 2025, 9:27am UTC](https://community.fibery.io/t/project-duration/8661/9 "2025-04-25T09:27:29Z")
This has done the trick, I’ve used a colour to differentiate the projects with the warning. As I develop my Fibery skills I can probably phase this out but for the time being it is perfect, thanks once again! ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [April 25, 2025, 9:39am UTC](https://community.fibery.io/t/project-duration/8661/10 "2025-04-25T09:39:19Z")
> [@fewlo](#): > > I’ve used a colour to differentiate the projects with the warning. Nice one - better idea than my suggestion 🤓 ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [April 29, 2025, 11:26am UTC](https://community.fibery.io/t/project-duration/8661/11 "2025-04-29T11:26:19Z")