[Status: Not Planned] Improved Critical Path Functionality
Critical Path functionality is essential for the complex projects of our organisation, but there is a great deal of manual workaround and effort required to make full use of the feature in Wrike.
It would be great if Wrike could:
- Show tasks that are on the Critical Path with a column in the table view - can only currently see the Critical Path on the Gantt chart with CP tasks highlighted red.
- View individual task float as a column in the table view - how long can a task be delayed before it impacts the Critical Path? (i.e. secondary and tertiary Critical Paths)
- Allow filtering to view only the Critical Path.
- Highlight if and where Critical Path is broken (when they don't reach back to the present) and the reason - to save having to manually find the Critical Path at the end and then follow dependencies back to where a task is no longer red and work out what dependency logic is breaking the CP.
- Where a Critical Path is broken, we still need to know the Critical Path from now up to that point - could the CP pick up again at the break and extend back to the present day? (Previous point of highlighting breaks essential)
- Automatically notify assignees that their task is on the Critical Path.
- Automatic notification of any changes to tasks on the Critical Path.
Thank you for your consideration (and sorry for saying "Critical Path" so many times).
For our organization this is the single most important feature that Wrike could implement as the number of projects grows within our business. Implementing this feature over time, incrementally, would be ideal - it doesn't need to be all at once.
Maintaining the end date of projects is vital and the tasks on our projects can change frequently, leading to manual effort and time to re-discover and re-connect the critical path.
We'd be keen to have a call with the Wrike team to explore the possibilities of implementing this type of feature.
The Critical Path is fundamental to managing projects, it appears as if the source data is already there in Wrike, but it just isn't represented in a useable way. It would be great to see this feature rolled out.
Adding support to the comments above. This is a great feature, it just needs additional usability. In particular, the ability to see float (which, as pointed out above, must already be there in the source data for the CP to be calculated).
Additionally, more clarity on how the critical path is calculate in Wrike would be helpful, especially as it relates to parent tasks. I don't always find it intuitive, despite building out a solid critical path analysis map prior to loading into Wrike.
Great suggestions, Gary Fallon!
Thank you for taking the time to share them with us. I checked with our product team, and there are currently no plans to implement this specific suggestion. We will keep you in the loop if anything changes.
Thank you, everyone, for the upvotes and use cases! 👍🏽
Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Torne-se um especialista em Wrike com o Wrike Discover
Basudha Sakshyarika Wrike Team member Torne-se um especialista em Wrike com o Wrike Discover
Basudha Sakshyarika even the ability to filter tasks by those on the critical path only would be extremely helpful for reducing the burden on project managers. Is such a small tweak in that direction something that you could reconsider? This change is smaller and would give us HUGE benefit.
The opportunity for product improvements was the reason we chose Wrike. We understand why the full ask is a lot but just some filtering would be transformational on large projects.
Hi Ross Ashley, I hope you don't mind me chiming in here on behalf of Basudha. We completely understand your point, and agree that this feature could be beneficial for some of our users. I will ensure that your comment is shared with the relevant Product Team. If there are any updates on this in the coming months, I'll be sure to notify you. Thanks again for your understanding and support.
Rohan V Community Team at Wrike Wrike Product Manager Torne-se um especialista em Wrike com o Wrike Discover
Rohan V Wrike Team member Torne-se um especialista em Wrike com o Wrike Discover
Rohan VBasudha Sakshyarika
I am new to the platform.
As I expect to begin implementing it in my organization, I would like to raise the importance of critical path data.
Specifically the ability to filter for critical tasks, and the table presentation of float per task are highly important.
We are managing long complex gantts with multiple dependencies, and the ability to have these feature available is very important.
Since these comments were raised almost a year ago, I was wondering if any progress is planned here?
Rohan V Community Team at Wrike Wrike Product Manager Torne-se um especialista em Wrike com o Wrike Discover
Rohan V Wrike Team member Torne-se um especialista em Wrike com o Wrike Discover