When making changes to sub project's duration, start or finish date, the changes do not roll up to master project's duration

Document ID : KB000045849
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:

When making changes to sub project's duration, start or finish date, the changes do not roll up to master project's duration. Why?

Steps to reproduce: 

  1. Create 2 projects: Master_project (12/1/2015 to 12/31/2015) and Sub_project (12/1/2015 to 12/7/2015) 
  2. Make Sub_project as the subproject of Master_project 
  3. Open Master_Project's Task tab. Click on Show all. 
  4. The Sub_Project will be shown as a row. 
  5. Configure the view so that Start and Finish date and the Duration is visible as columns. 
  6. Now again go to Project List page and open the Sub_Project. 
  7. Change Sub_project finish date: 12/7/2015 to 12/14/2015, then save 
  8. Follow the Step 3 and 4.

Expected Result: Sub_Project row will be showing the updated finish date and he duration accordingly.

Actual Result: Sub_Project row is still showing the old Finish date and Duration.

Environment: 14.3, 14.4

 

Answer: 

If master project has schedule dates as (1/1/2016-1/31/2016) and sub project has schedule dates as (1/1/2016-3/31/2016), then adding sub project to the master will increase the master project's schedule. Reason for this behavior is at the time of adding we know for sure that there is a dependency on the sub project. 

If master project has schedule dates as (1/1/2016-1/31/2016) and sub project has schedule dates as (1/1/2016-1/15/2016), then adding sub project to the master doesn't have any impact. After adding sub project, updating its schedule to (1/1/2016-3/31/2016) also doesn't have any impact on master. 

We are observing the same / similar behavior in case of task list page as well. Reason is the sub project's schedule can change because of several reasons which are not related to the master project. 

A project can be child of several other projects and change of schedule of this project should not impact the schedule of all its parent's projects. 

This is working as per design. 

 

Additional Information: 

There was a request (CLRT-79446) raised to the Sustaining Engineering team regarding this scenario, and they confirmed that this is not an Issue with the Product. If users/customers want this to be implemented, then they can raise an Idea for the same.