Tasks that are part of a Schedule, can have an associated Predecessor Task, or Task Dependency, from within the same Schedule.
With the release of the new schedule grid view in April, and the Gantt view in May, Task dependencies are the latest step in our vision to make the planning of work easier, faster and more visual.
Please review this article for a walk-through of this recent feature.
How to Access
Any Task can have one predecessor, and more than one dependency.
To add a predecessor or dependency, you will need to be on a detailed view of the Task. This is most easily done from the Gantt view, where the Task will open for you in a new browser tab.
For this example, let's say I want my Image research Task to be a predecessor of the Image sourcing Task, and the Image acquisition Task to be dependent on Image sourcing. Click into the Image sourcing Task.
Here on the detailed view of this Task, I see dependency options in the bottom right corner.
Create a Predecessor
- Clicking New Predecessor opens up a field through which I can pick from the other Tasks on the same Schedule. Click Create Linkage to save your selection.
Note that the system will not let you do anything goofy - for example above, because my Task "Image research" is the predecessor here, I cannot select it to also be the dependency.
And should I create a link where the dates don't make logical sense, the system will give me a visual colour queue that things may be amiss. Above, my Task that's due in early September, should probably not be the predecessor for my Task due in late July.
View the Dependency Lines
Go back to the browser tab with the Schedule view. Click the "Gantt View" button to refresh this page.
Q: If Task A is a predecessor to Task B, will the system prevent someone from working on Task B until Task A is complete?
A: Nope! The use of a Task predecessor or dependency will not lock any Task down from being worked on. The predecessors and dependencies give you visual insight into linkages between Tasks on a Job.
Q: Do Tasks have to be on a Schedule for me to add a predecessor or dependency?
A: Yes. The Task(s) must be part of a Schedule in order to have dependency linkages.
Q: Can a Schedule Template have Task Dependencies on it?
A: You bet, and those dependencies will copy over if you create a new schedule, based on a template.
Q: How many predecessors can a Task have?
Q: How many dependencies can a Task have?
A: There is not a set limit, but any Task can only be a dependent of another Task one time. Also keep in mind that you may end up not improving the clarity of your work if you end up with too many dependencies on a single Task.
Q: Can I find Tasks in the system based on if they have a predecessor or dependent?
A: Not at this time.
Q: Do the Tasks need to be in a certain status (Assigned, In Progress etc) for me to add or remove dependencies?
A: No they don't. The Job will need to be in an active state though.
Q: Can I see a history of a Task being made or unmade a predecessor or dependant of another Task?
A: Not at this time. You can limit who can create these linkages though, if you have concerns over staff adding or deleting Task connections when they shouldn't.
Q: Do I have to use this feature on all or none of the Tasks within a Schedule?
A: Nope! Use task dependencies on 2 Tasks in a Schedule, all the Tasks, or none. Up to you.
Who has Access?
The ability to associate a predecessor or dependency to a Task is permission based. Users will need 5 particular permissions, within the Tasks permission grouping:
- Task | Add
- Task | Delete
- Task | Delete Others
- Task | Update
- Task | Update Others
Lacking any one of these permissions, will mean the user cannot use the dependencies feature.
We welcome your questions or concerns: firstname.lastname@example.org