Using Programme App in a Hybrid Environment with P6
When P6 is used to populate Tasks and some updates are supported in Action Tasks
Tools like P6 support various things like:
- Task Dependency (blocking or blocked by)
- Task Resource Associations
- WBS
When synchronising P6 with Deep Space, most fields and relationships are captured from P6 along with all associations.
Use of Assignee Field
P6 does not have the concept of a singular "Task Owner", known as an Assignee in Deep Space.
Once Deep Space Action Tasks have been created by P6 synchronisation, the end user should update the Assignee field to ensure notifications and My Actions works effectively.
What to Update in Deep Space
When importing a new version of P6 Programmes, the following Deep Space Task fields are 'persistent' across updates:
- Task Assignee
- Estimated Dates
- Comments
- Watchers
- Extra Associations (non Action task associations)
In general, other data is overwritten by P6 on subsequent imports.
Notifications
You will be notified when:
- You are the Assignee (Task Owner)
- You are a Watcher
- You are Resource attached to a task*
* in the project summary email you will get notified about actions you are a resource on IF the Resource-User mapping has been done.
My Actions
The My Actions page is the best way to quickly manage tasks in bulk.