A Constraint is a Project-level record used to mark an external dependency or a fixed date that can't move — like a Milestone, it has no duration, and it exists to flag something outside the team's control (a permit, a delivery, an inspection date) that the Plan needs to account for. Constraints can still be assigned to Teams and connected to other Tasks like any other Project element.
Visually, a Constraint uses the same card structure as a Task and Milestone, with the same inverted dark-background, light-text color scheme as a Milestone for easy distinction in a dense Plan. It has its own distinctive icon (a stylized hourglass) and since it has no duration, it's displayed on a single date rather than spanning a range.
Constraints also have four fields that Tasks do not:
- Created
- Required
- Promised
- Resolved
These fields are calculated in the Project Insights to monitor the lifecycle of Constraints in the Project.
- Drag and drop from the Constraint icon on the Toolbar (or click on the Constraint icon and double click in the general area of where you would like it to be)
- Click into the fields in the rest of the Editor or press Tab on your keyboard to jump to the next field and fill it out with the necessary information
- Click the “Save & Close” button
- Adjust the Constraint card to make sure it is situated in your desired spot
From this point, however, other users can open the Constraint and add to the Promised and Resolved date fields to better track the lifecycle of the Constraint.
Comments
0 comments
Article is closed for comments.