So in the above example if one of those tasks was split to be. But the summary will take into account the split time because the finish date of the task moved out. If you split a task the duration of the task will only show as the actual work duration and not count the split time. If you have 5 sub tasks all starting and finishing in the same day the Duration summary duration will be 1 day. However you also have to consider the summary task is behaving correctly. I then inserted a new row and recreated the summary task. The way I fixed it I out-dented the sub task to the same level and deleted the summary task. regards, Colinįrom: “Robert Kelly via ms-project-l” Reply-To: To: ColinPM Subject: RE: Summary tasks not calculating subtask dates Date: Sat, 14:27:47 GMT More information may be needed, the version on MSP to start with, and what/which columns are not rolling up? I experienced a glitch in 20 where a summary task I just don’t like it when Project gets the better of me. Iv’e taken off all constraint dates and set the project start date as i thought this could be the issue before asking for help but alas also to no avail. i’ve also tried cut and pasting all the tasks at once into a new file, to no avail. but was curious to know why Project was reacting this way. If worst comes to worst i will re enter all the tasks one by one. if i change the summary task dates when it is a normal task at this point, then make it a summary task, the dates stay as per when it was a normal task. I created this plan from several others by cut and pasting tasks. Ive tried out denting /redenting but the dates still don’t roll up.
Thanks for the reply, I am using MS Project 2003, The start and finish date columns are not rolling up, and as a summary task these are locked. These will make the summary task look like If you have applied actual work to some tasks and then go backĪnd change the predecessors/successors, or re-level, some WED the task duration would still be 1d but the Summary would Summary will take into account the split time because the finishĭate of the task moved out. The actual work duration and not count the split time. If you split a task the duration of the task will only show as In the same day the Duration summary duration will be 1 day. If you have 5 sub tasks all starting and finishing
However you also have to consider the summary task is behavingĬorrectly. The way I fixed it I out-dented the sub task to the same levelĪnd deleted the summary task. Glitch in 20 where a summary task stopped I know that if I insert a Summary Task line to encapsulate the two main scopes of the project and then assign the task calendar to this task the duration will be measured correctly.More information may be needed, the version on MSP to start with,Īnd what/which columns are not rolling up? I experienced a When I insert the line 'Project Summary Task' the project summary task does not calculate the total duration correctly. These times are also reflected in the task calendar which I have assigned this calendar to all tasks. Via the calendar options I have adjusted this to reflect 2 shifts patterns working 9hr/day (06:00 to midnight = 18hrs/day), six days per week = 108hrs, 24 days per month. I have adjusted the project calendar via the 'Calendar Options for this project' setting and also the Task calendar. roll up the durations of all summary tasks. When I put together the project schedule and then insert the line 'Project Summary Task', the duration column does not display the correct durations i.e. I'm hoping someone can assist me in solving a problem I am having with using Project Summary Task (Line 0) to provide the duration for an entire project.
0 kommentar(er)
