jerryreid
commented
9 years ago This is how Milestones PM works out of the box and our experience has been that each Salesforce customer wants to sync up the dates (up or down a work breakdown structure) differently. Thrown in milestone and task dependency logic and you have yourself a bit of a nightmare of code to manage. This is what we designed Rollup Helper for. You can use Rollup Helper in a variety of ways as follows:
1) Sync project task dates to milestones. 2) Sync milestones dates to project dates. 3) Count number of log items (unresolved issues) to prevent project closure. 4) Create new project / rollup metrics on the project page. 5) Rollups budgets or other costs. etc.
There is a free version that supports 3 scheduled rollups and the paid version support unlimited, real-time rollups for CRM-wide usage.
You can get it from the AppExchange: http://appexchange.salesforce.com/listingDetail?listingId=a0N30000009i3UpEAI
Sorry for the commercial, but this is really the best solution to solve this problem without having to dabble in the code to change how the rollups work in your org.
When populating a milestone with tasks, the milestone kickoff date/due date should be linked to the task that has the earliest kickoff, and the latest due date.
Right now, when you create a task list and have set all of your dates, you then have to manually set the over all milestone kickoff/due dates to match the ones in the task. For ex. if your last task ends on OCT31, you have to set the milestone due date to OCT31. IF there is a delay, and you add 1 week to the tasks dates NOV7, your milestone due date will still be showing OCT31. You have to manually change the date.