What is a Conflict?
A Conflict indicates a contradiction between Start and Due dates of at least two project work items.
The following are several examples of a Conflict:
- A hammock (parent item) has a manually set Due date but one (or more) of its sub-items finishes after that date
- Task T1 has a manually set Due date and Duration. Task T1 depends on task T2 that has a Due date that prevents T1 to be finished on time.
- Task T1 has a manually set Start date. Task T1 is dependent on another task T2 whose Start or Due date is earlier than the Start date of task T1.
In case of conflict situations, the system does not automatically move planned Start or Due dates accordingly, but rather raises an indication of a conflict.
Affected Work Items
There are two types of Conflict indicators in the system:
- Impacting – indicated by the symbol . Image is indicated on the work item which created the conflict.
- Impacted – indicated by the symbol . Image is indicated on the work item which is affected.
The If a work item that causes conflict is on the critical path, Impacted work items are marked recursively.
Alerts are generated for conflicts on the relevant impacting and impacted work items.
How can you handle a Conflict?
As described above, Conflicts are created as a result of contradiction of Start or Due dates between two entities.
To Resolve a Conflict:
- Change (or request to change) due date of impacted work item to synchronize with the impacting work item’s due date.
- Change due date of impacting work item to synchronize with the work item’s due date constraint. You can reduce the duration of the work item (and possibly assign more resources) or remove dependencies, etc.
- Unset Manually Set flag where relevant and acceptable
When a conflict is resolved, the appropriate alert is marked as resolved.