When using projects, if a project task has a child project task associated to it several fields become read only. The Project team would like to use parent/child project tasks independently for the purposes of calculating resource costs, but as the fields are set to be read only on a parent project task this isn't possible.
I've been able to disable the BRs and properties which calculates and manages the roll up of data from the child project task to the fields on the parent project task form, but certain fields on a parent project task remain to be read only when a child project task is associated to it.
These fields are:
- effort
- work_effort
- percent complete
- duration
- work_duration
Is there a way to prevent these fields from being set to read only when a project task has a child associated to it? I've gone through the client scripts and UI Policies applied to the table pm_project_task (including inherited tables like task) and can't find anything there that controls this behaviour. I've gone through the product docs but can't seem to find anything that defines this read only fields behaviour:
https://docs.servicenow.com/bundle/washingtondc-it-business-management/page/product/project-manageme...
Why has this been requested? The project teams are using rate cards on project tasks, which use different costs per hour dependent on the rate card that has been applied to the task for calculating internal costs and charging to external customers. A parent project task can be allocated to x rate card (e.g., PM) for managing the activity included in the child tasks, which have a different rate card set with different resource costs (e.g., developer). As the roll up of the work_effort from the child task was over-riding the parent project task then the actual effort/cost of the parent task couldn't be set via the 'work_effort' field so this has been disabled. However, as the parent project fields are now read only the work_effort (i.e., number of hours spent) spent the parent project task can't be defined.
