It seems that you are looking for a hammock task (like an LOE activity in P6). MSP doesn't officially have one. The recommended workaround has been to copy|paste-link the start and finish dates from a single start-governing task and a single finish-governing task to the start/finish dates of the task that you want to turn into a hammock. Obviously, this task shouldn't have any other logic attached to it. The duration will automatically adjust to the linked dates, and a fixed-units task should automatically increase or decrease the work as dictated by the new duration.
Note: although this workaround is widely recommended, it's pretty flaky, difficult to audit, and seemingly more subject to corruption. It was never a reliable long-term solution for me, and I gave up on "MSP hammocks" years ago as a result. The main option is manual (or macro-driven) adjustment of task duration. I've tried playing around with using two logic-driven dummy milestones to drive a dummy summary task (resource loaded), but I haven't used it enough to recommend an approach.
Member for
21 years 8 monthsWe call it Hammer's Rule - If
We call it Hammer's Rule - If it wont fit, hit it with a hammer until it fits.
LOL.
Member for
19 years 10 monthsHi EmmaDecrease the work
Hi Emma
Decrease the work pattern hours from 8hrs per day to 7.5 hrs per day and the duration will increase.
Best regards
Mike Testro
Member for
18 years 11 monthsHi Emma, It seems that you
Hi Emma,
It seems that you are looking for a hammock task (like an LOE activity in P6). MSP doesn't officially have one. The recommended workaround has been to copy|paste-link the start and finish dates from a single start-governing task and a single finish-governing task to the start/finish dates of the task that you want to turn into a hammock. Obviously, this task shouldn't have any other logic attached to it. The duration will automatically adjust to the linked dates, and a fixed-units task should automatically increase or decrease the work as dictated by the new duration.
Note: although this workaround is widely recommended, it's pretty flaky, difficult to audit, and seemingly more subject to corruption. It was never a reliable long-term solution for me, and I gave up on "MSP hammocks" years ago as a result. The main option is manual (or macro-driven) adjustment of task duration. I've tried playing around with using two logic-driven dummy milestones to drive a dummy summary task (resource loaded), but I haven't used it enough to recommend an approach.
Good luck, tom