Conflict Warnings List

• Dependency Conflicts
  • Replanned Tasks
  • Relationships Other Than Finish-to-Start
  • Lag/Lead Time
• Crew Size Conflicts
• Working/Non-Working Day Conflicts
• Swimlane Conflicts
• Constraint Conflicts
  • Constraint Made After Required Date
  • Promised Date After Required Date

There are several types of conflicts that will appear as you use Hoylu Plans, and this article will provide you with a comprehensive list of those conflicts and how to resolve them. 

Dependency Conflicts

Replanned Tasks

Figure 1. Dependency conflict from the replanning of an incomplete Task.

Dependency conflicts occur when there is an overlap between two dependent Tasks. A red border will be displayed around the Tasks, representing a warning for the team to review and adjust, depending on the scenario.

To resolve this conflict, you must either confirm the Tasks can run in parallel or drag and drop the dependent Task to another day (or use Assistive Rescheduling).

Conflict Warning: Red Border and Red Connection Icon

Reason: Dependencies in Hoylu are Finish to Start as a Default, so Hoylu assumes your dependent Tasks cannot run in parallel

Resolution: Click on red Connection Icon to open Resolve Conflicts pop-up (or manually drag the tasks out to a another day)

Figure 2. Resolve conflict by moving conflicting elements.

1. Click on the red Connection icon on the top left of the Task
   
   
2. Find the conflicting Task on the list, marked in red
   
   
3. Click on the triangular warning sign 
   
   
4. Choose either Confirm that elements can run in parallel or Move conflicting elements in the Resolve Conflict pop-up
   
   
5. Click on the checkbox to Apply for all conflicts of selected element(s) (optional)
   
   
6. Click on the Update button

✏️  Note: Hovering over dependent Tasks will show non-conflicting Tasks with a blue outline like normal, but conflicting Tasks with an orange outline.

Relationships Other Than Finish-to-Start

Hoylu currently shows finish-to-start relationships when creating connections between Tasks as a default. You can, however, modify the connection type to account for lag or allow other types of relationships.

Conflict Warning: Red Border and Red Connection Icon

Reason: Dependencies in Hoylu are Finish to Start as a Default, so Hoylu assumes your dependent Tasks cannot run in parallel

Resolution: Click on the Dependency line to change its relationship type from finish-to-start to start-to-finish, start-to-start, or finish-to-finish. 

Figure 3. Start to Start relationship.

Review this article to see more about different dependency or relationship types and lag/lead times.

Lag/Lead Time

If you have specified a lag or lead time on Tasks, Hoylu will make sure that the amount of days between or overlapping on Tasks are honored unless you choose to change it.

Conflict Warning: Red border and Red Connection Icon

Reason: Lag or lead time has been violated

Resolution: Move conflicting elements or adjust lag/lead time

Figure 4. Resolve Lag conflict through Connection menu.

1. Click on the Connection line or the red Connection icon
   
   
2. Click on the red warning triangle
   
   
3. Click on Move conflicting elements to adjust the downstream item and honor the lag or click on Adjust Lag/Lead to change it

Crew Size Conflicts

Figure 5. Reduce Crew Size on the Task.

The crew size specified on individual Tasks is calculated against the total crew size specified in the Team Settings on a per day basis, so when a Team's task overlaps with another and causes the total crew size to be over the limit, you will be required to either reduce the crew size or ignore one of the Tasks in the total crew size calculation.

Conflict Warning: Red Border and Red Crew Size Icon

Reason: Task has crew size over limits or there is another Task on the same day that is putting team's total crew size over limit

Resolution: Click on red Crew Size icon to either reduce the crew size to a number that keeps the crew total for the day at or under limits, or ignore Task in the crew size calculation

Figure 6. Ignore Task in crew size calculation.

1. Identify the Task whose crew size needs to be adjusted or ignored
   
   
2. Click on the red crew size icon on the right side of the Task
   
   
3. Click on either option to reduce or ignore the crew size calculation (the reduce option will be grayed out if the crew limit has already been reached by other Tasks)
   
   
4. Click the Confirm button

Working/Non-Working Day Conflicts

Figure 7. Tasks on Non-Working Days.

Tasks are automatically set to skip weekends and holidays so unless the option to Skip weekends and holidays is deselected in the Task Editor, the Task will be flagged. 

Conflict Warning: Red Border

Reason: First day of Task is scheduled on a non-working day

Resolution: Move Task to either a day earlier or to the next working day

Swimlane Conflicts

Figure 8. Resolve Swimlane conflict warnings by clicking on the Swimlane label.

If you add a label to a Task that matches an existing Swimlane label, Hoylu will automatically recognize that Task needs to be in requisite Swimlane. This will happen only if you have added Swimlane labels, which you can learn about more in this article. 

Conflict Warning: Red Border, Swimlane label has a warning triangle

Reason: An imported or manually-added label is conflicting with a Swimlane label

Resolution: Move Task to the correctly-labeled Swimlane or change the label

1. Click on the Swimlane label with the triangular warning symbol
   
   
2. Decide if you want to change the Task label to match the Swimlane or move the Task to the Swimlane its label matches
   
   
3. Confirm if the date on the Task also needs to be adjusted
   
   
4. Decide if you want to do this for all suitable elements
   
   
5. Click the Update button

✏️  Note: This will happen regardless if you have Swimlane labels visible (in the Plan Settings).

Constraint Conflicts

Constraint Made After Required Date

Figure 9. Create a new Constraint after its Required Date.

If you create a Constraint that was Required before its Created Date, Hoylu will not show it on the Plan with a red border but rather with red text in the Constraint Log. This is primarily for users who want to show an archive view or history of Constraints.

Conflict Warning: Red Promised and Required Dates in Constraint Log

Reason: Constraint created after Required Date

Resolution: None

Promised Date After Required Date

Figure 10. Resolve Required or Promised Dates on Constraint conflict.

Using Constraints may require some back-and-forth between different parties of the project. This article will provide more insight on how this works so you can better understand how to resolve this conflict.

Conflict Warning: Red Border on Constraint and warning triangle on Promised Date Label

Reason: Promised Dates need to be on or before the Required Dates

Resolution: Promised Date or Required Date needs to be adjusted

1. Click on Status button on the right side of the Constraint
   
   
2. If you are the creator, you can Accept Promised Date; if you are the responsible party, you can Accept Required Date
   
   
3. The Task will move depending on which action is taken