We are using Structure's Gantt chart to plan our production.
The current Gantt chart we have does not highlight any tasks in red as the critical path, even though we have critical path ticked.
What are the requirements for a task to be shown on the critical path, must all tasks have dependencies?
Hi Camille, and welcome to Community!
I found the following in the documentation about Structure. Have you confirmed that you have the critical path highlighting showing?
You can show or hide critical path highlighting using the Options menu in the Gantt toolbar.
Thank you for your post.
My colleague Egor provided a reply to the Service Desk request you logged with us but I wanted to post here as well to make sure you received it.
Critical Path, by definition, is the sequence of tasks which when delayed affect the Finish Date of the whole Project. It is a set of critical tasks and may or may not form a path. A task is considered critical if its "Slack" is equal to or less than 0. Slack is the amount of time a task can be delayed without delaying the whole Project.
I don't know if that might be the case for you but if you have an opening in the sequence of two tasks, it cannot be a Critical Path, as the first task has some allowance for a delay.
I hope this helps. Otherwise, perhaps you can share a screenshot with us on the ticket you logged via our Service Desk so we can further assist you.
Critical Tasks are those tasks which, when delayed, will delay the finish of the whole project. A Critical path is a set of critical tasks. By definition, this would be calculated based on the latest milestone.
Could you tell me a bit more about your use case? Perhaps I can share with our Product Team to see if there's a possibility to improve the feature.
Your definition of critical path (i.e. set of tasks with zero slack) works perfectly when the limiting factor in creating an end to end plan is a set of fully interconnected tasks.
In many projects, there are other variables to contend with (i.e. externally driven dates that define when tasks can start).
If you have such a restriction during a late phase of a project then your critical path functionality just highlights the last set of tasks with zero slack (exactly the correct behaviour as you've currently defined it).
What would be really useful would be to have a way to highligh the critical path for selected milestones within a project (should just be the same logic regarding zero slack, just using a milestone as the limiting condition rather than project end)
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events