Blazor Gantt Chart Example - Task Constraints
TaskId | Job Name | Constraint Type | Constraint Date | Start Date | End Date | Duration | Progress | Dependency |
|---|
| 1 | Software product release | As Soon As Possible | 1/7/2026 08:00 | 2/6/2026 05:00 | 23 days | 31 | ||
| 2 | Requirements gathering | As Soon As Possible | 1/7/2026 08:00 | 1/8/2026 05:00 | 2 days | 100 | ||
| 3 | Stakeholder approval | Must Start On | 1/9/2026 08:00 | 1/9/2026 08:00 | 1/9/2026 05:00 | 1 day | 100 | 2FS |
| 4 | UI design | Start No Earlier Than | 1/12/2026 08:00 | 1/12/2026 08:00 | 1/13/2026 05:00 | 2 days | 100 | 3FS |
| 5 | Architecture design | Must Start On | 1/14/2026 08:00 | 1/14/2026 08:00 | 1/14/2026 05:00 | 1 day | 100 | 4FS |
| 6 | Backend development | Must Start On | 1/15/2026 08:00 | 1/15/2026 08:00 | 1/19/2026 05:00 | 3 days | 75 | 5FS |
| 7 | Frontend development | Start No Earlier Than | 1/15/2026 08:00 | 1/15/2026 08:00 | 1/19/2026 05:00 | 3 days | 65 | 5FS |
| 8 | API integration | As Soon As Possible | 1/20/2026 08:00 | 1/21/2026 05:00 | 2 days | 0 | 6FS,7FS | |
| 9 | Database optimization | Start No Later Than | 1/20/2026 08:00 | 1/20/2026 08:00 | 1/21/2026 05:00 | 2 days | 0 | 6FS |
| 10 | Unit testing | As Soon As Possible | 1/22/2026 08:00 | 1/22/2026 05:00 | 1 day | 0 | 8FS | |
| 11 | Integration testing | Start No Earlier Than | 1/23/2026 08:00 | 1/23/2026 08:00 | 1/26/2026 05:00 | 2 days | 0 | 10FS |
| 12 | Security review | Start No Later Than | 1/23/2026 08:00 | 1/22/2026 08:00 | 1/22/2026 05:00 | 1 day | 0 | 9FS |
| 13 | Performance testing | Finish No Later Than | 1/27/2026 05:00 | 1/26/2026 08:00 | 1/27/2026 05:00 | 2 days | 0 | 11FS-1 days |
| 14 | QA signoff | Must Finish On | 1/28/2026 05:00 | 1/28/2026 08:00 | 1/28/2026 05:00 | 1 day | 0 | 12FS,13FS |
| 15 | Release preparation | Must Finish On | 1/30/2026 05:00 | 1/29/2026 08:00 | 1/30/2026 05:00 | 2 days | 0 | 14FS |
| 16 | User documentation | As Late As Possible | 1/29/2026 08:00 | 1/30/2026 05:00 | 2 days | 0 | 14FS | |
| 17 | Production deployment | Must Start On | 2/3/2026 08:00 | 2/3/2026 08:00 | 2/3/2026 05:00 | 1 day | 0 | 15FS+1 day,16FS+1 day |
| 18 | Go-live validation | Start No Later Than | 2/4/2026 08:00 | 2/4/2026 08:00 | 2/4/2026 05:00 | 1 day | 0 | 17FS |
| 19 | Production monitoring | As Late As Possible | 2/5/2026 08:00 | 2/6/2026 05:00 | 2 days | 0 | 18FS | |
| 20 | Project closure | Finish No Later Than | 2/6/2026 05:00 | 2/6/2026 08:00 | 2/6/2026 05:00 | 1 day | 0 | 19FS-1 days |
Jan 01, 2026 | Jan 04, 2026 | Jan 11, 2026 | Jan 18, 2026 | Jan 25, 2026 | Feb 01, 2026 | Feb 08, 2026 | Feb 15, 2026 |
T | F | S | S | M | T | W | T | F | S | S | M | T | W | T | F | S | S | M | T | W | T | F | S | S | M | T | W | T | F | S | S | M | T | W | T | F | S | S | M | T | W | T | F | S | S | M | T | W | T | F |
This sample demonstrates how to schedule and manage a software product release using the Blazor Gantt Chart. It showcases how task constraints can be applied to control task scheduling and enforce project timeline requirements.
In Gantt Chart, task constraints define the rules that limit a task's start or finish date based on project scheduling requirements.
The supported constraint types include:
As Soon As Possible- Schedules a task to start as early as possible based on its predecessors and project schedule.As Late As Possible- Schedules a task to finish as late as possible without delaying successor tasks or the overall project timeline.Must Start On- Forces a task to start exactly on the specified constraint date.Must Finish On- Forces a task to finish exactly on the specified constraint date.Start No Earlier Than- Prevents a task from starting before the specified constraint date.Start No Later Than- Requires a task to start on or before the specified constraint date.Finish No Earlier Than- Prevents a task from finishing before the specified constraint date.Finish No Later Than- Requires a task to finish on or before the specified constraint date.
Constraints can be assigned to tasks by mapping the ConstraintType and ConstraintDate properties of GanttTaskFields. Constraint information can also be modified through the task edit dialog, enabling scheduling restrictions to be updated dynamically.
When a task violates an assigned constraint, the Gantt Chart displays a scheduling conflict dialog containing details about the violation. The dialog provides options to either cancel the action and preserve the existing schedule or remove the conflicting constraint and apply the schedule change. This helps maintain accurate scheduling while respecting project deadlines and dependency relationships.
For details on task constraints, constraint types, scheduling conflict handling, and constraint validation in Gantt Chart, refer to the documentation.