[Status: Not planned] Project/Folder Dependencies

Yes please! This would be such a great feature!

This feature will help our team be better organized. The ability to add project dependencies is greatly needed. I upvoted in May of 2018 and commented then. The need remains. Please consider putting in front of your product development team for consideration. 

Hi Carole Charrade, Denise Miller, thank you both for adding your support for this suggestion 🙌🏼

Cansu Community Team at Wrike Wrike Product Manager Learn about Wrike’s killer features and best practices with our Online Training Webinars

Cansu Wrike Team member Learn about Wrike’s killer features and best practices with our Online Training Webinars

This came up in a meeting today - it's a feature that really would solve a lot of our operational and reporting needs.

Hi Leann Lewis, thank you for sharing your feedback here, it's been passed on to our Product team 👍🏼

Cansu Community Team at Wrike Wrike Product Manager Learn about Wrike’s killer features and best practices with our Online Training Webinars

Cansu Wrike Team member Learn about Wrike’s killer features and best practices with our Online Training Webinars

Thank you @...! Would it help for me to provide some clear examples of what we are hoping to accomplish? We currently do this "project dependency mapping" separately in LucidCharts.

Hi Leann Lewis, of course, please do share your use case(s) here. All use cases shared help understanding the need, and popularity of a suggestion even though this is currently not planned by our Product team. 

Cansu Community Team at Wrike Wrike Product Manager Learn about Wrike’s killer features and best practices with our Online Training Webinars

Cansu Wrike Team member Learn about Wrike’s killer features and best practices with our Online Training Webinars

@... Up-vote for this feature! We run all of our projects through Wrike and having the ability to roadmap/plan with project dependences would add so much value to Wrike's reporting capabilities.

Hi Ashley Anderson, welcome to the Community! 🤗
Thanks a lot for supporting this idea! I'm passing your feedback to our Product team  Please make sure to upvote the original post above if you haven't yet - the number of votes helps the team understand how popular the suggestion is. Here's more detail on that, but please let me know if you have any questions! 
If you'd like to know what this Community has to offer, please check out our New to Community forum 👋

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

Add another vote for this feature from me, please. This is a feature I have missed since converting my plans from MS Project to Wrike. The workaround of linking to tasks within a project is cumbersome and makes for less readable plans.

Hello Chris Broshears, thank you for adding your support here, and welcome to the Community! 

I've passed on your feedback to our team, and if there are any updates in relation to this request, we'll be sure to share them here.

In the meanwhile, if you'd like to discover our Community, please check out our New to Community forum 🙋🏻‍♀️

Cansu Community Team at Wrike Wrike Product Manager Learn about Wrike’s killer features and best practices with our Online Training Webinars

Cansu Wrike Team member Learn about Wrike’s killer features and best practices with our Online Training Webinars

@... here are two primary use cases for us:

1) Often times large implementation are broken into projects executed by different teams. So, for example, for the build of a new software or technical project there is a requirements gathering phase, stakeholder meetings, etc (often handled by project management, SMEs and stakeholders). From there the technical build phase consists of technical planning and project build. Beyond that there is rollout planning, training, support planning and support team hand off. Often, each phase is effectively a sub project and the start of one phase is impacted by the end date of the priot phase. For purposes of dev work, for example, a FULL project implementaiton may take a year, but the dev buil phase may consist of 3 - 6 month of that time so the ability to set a "project end date" for the technical portion alone for tracking purposes would be ideal. Right now we sort of handle this with projects within projects - but there is alot of manual maintenance of dates, no way to chart project dependencies, etc.

2) This use case is more complex and doesn't have as clean a work around. We often have full scale implementations that must be complete before the first phase of a future project can even be started. For example - in order to do a certain series of automated sales reports we have to complete two products: one that tracks revenue data granularly by specific metrics (we have this done), and another that integrates with our HRIS and maintains an org chart in a database (this one is in progress). As it stands, completion of those two prjects are pre-requisites for 4 - 6 other projects that measure operational performance regionally, sales driver performance and a number of other metrics. Those projects are all for separate business divisions with unique requirements - but they have overlapping pre-requisite infrastructure. Currently we map all of these global dependencies in LucidCharts to make sure that we are effectively prioritizing projects and identifying/measuring the long term impact of shifting project timelines.

I could also see this being useful for cross functional teams within technical developement, where an infrastructure team may have to set up servers and network infrastructure before a dev team can start to build out a product.

I also wanted to mention that I did take a look at the workarounds suggested. In order to do that effectively we would have to build out timelines for all future pojrects. We have an incoming docket of over 200 projects. We can identify project dependencies but going in and creating full scope plans for all of those when we may not not be starting on them for a year seems like a waste of time. Especially considering the fact that sometimes projects become moot or irrelevant in the face of business or technology changes. We need the project dates to move and to be able to RoadMap across a series of inter-dependant projects without necessarily having the entire scope for every single piece planned out.

Hello Leann Lewis, thank you for sharing your use cases in detail here. I've passed on the use cases you've shared here to your CSM in order to discuss how we can meet your needs better. 

Cansu Community Team at Wrike Wrike Product Manager Learn about Wrike’s killer features and best practices with our Online Training Webinars

Cansu Wrike Team member Learn about Wrike’s killer features and best practices with our Online Training Webinars

This would be a game-changer for us. Many of our projects are built with subprojects. Subproject 2 cannot begin until Subproject 1 is complete.

Hi Ashley Fischer, thank you for taking the time to add your support here 🙋🏻‍♀️

Cansu Community Team at Wrike Wrike Product Manager Learn about Wrike’s killer features and best practices with our Online Training Webinars

Cansu Wrike Team member Learn about Wrike’s killer features and best practices with our Online Training Webinars

Yes please! We have projects dependent on projects and it would be so great to have the ability to say "Project B" can't start until "Project A" is completed (FS)... but predecessors (dependencies) are only available at task level not project.

This should be a great feature to plan the priority work 1st and let the 2nd priority project start once the 1st project has been completed based on this dependency.

We have 2 years of requests for being able to add dependencies at the project level.  Why does Wrike not listen? 

@... in the Product feedback forum - could you all possible separate the launched features from everything else? There is too much to navigate there. it's hard to tell which unlaunched / unplanned features are high on the vote list without digging through everything forever. The pinned posts also confuse the sorts and the view on that page. Some of those pinned posts are for launches from over 6 months ago.

Hi Leann Lewis! Thanks a lot for your feedback on how the forum is structured, it's very valuable to us! We don't have subfolders or subtopics on the platform currently but we'll keep your feedback in mind 👍 I would definitely recommend searching in the forum to find some specific topics to upvote. You can click "Community" to only search in the forums, and then "Product Feedback" to only search in this forum: 

I hope this helps! Thanks again for your feedback 🙌

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

Hi everyone! Ilia here from Wrike’s Product team 👋

Thanks to all of you for continuously sharing your feedback and supporting the idea of folder and project dependencies. 

Based on the feedback we’ve received from you here and elsewhere, my team does agree that this would be a useful addition for some of Wrike users. Unfortunately, this improvement does not fit into this year’s roadmap, and I’d like to share some context on why the “Not Planned” status remains. 

First of all, my team is highly focused on improvements related to the Table View. Some of you may have seen that we’ve been recruiting customers for interviews to discuss potential enhancements, especially for those of you who are used to working with List View. After conducting multiple interviews and gathering lots of input, we have designed and are implementing big improvements for the new version of Wrike’s Table View, and we will be sharing more news on this topic in the coming months. 

The second reason for not working on this feature is that in the original architecture of Wrike projects were not designed to ever have dependencies, so this would require a major change that is not in our capacity at the moment.

Having said all that, I’d like to thank you all again for taking the time and sharing your feedback with us. We will keep this idea on our radar for potential future improvements. 

Ilia Kreys Community Team at Wrike Wrike Product Manager Learn about Wrike’s killer features and best practices with our Online Training Webinars

Ilia Kreys Wrike Team member Learn about Wrike’s killer features and best practices with our Online Training Webinars

Add my vote to this.  It would be extremely helpful to dependencies between projects and folders.

By doing so Wrike could really be a competitor to professional planning packages such as Primavera and MS Project. It is really a shame Wrike doesn't see this as a huge opportunity. It's a functionality that could open a lot of doors and make Wrike suitable for a much wider range of applications.

Hi Gary Carreon, Nils Troll, thanks for taking the time to add your thoughts here. We've passed this on to the team 👍

Elaine Community Team at Wrike Wrike Product Manager Learn about Wrike’s killer features and best practices with our Online Training Webinars

Elaine Wrike Team member Learn about Wrike’s killer features and best practices with our Online Training Webinars

This would be very helpful as our business is based on projects - project b cannot start until project a finishes therefore once project a finishes, and assuming project b is already created, the dates on project b would be updated rather then having to be manually modified.

Welcome to the Community Eric Sebor 👋

Thank you for supporting this suggestion! It's not planned currently, but this is on the team's radar and if there are any updates here in the future, we'll make sure to let you know 👍

Please check out our New to Community forum if you'd like to know what this Community has to offer.

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

Nils Troll I agree. This really is like having a car without air conditioning in the summer in southern Alabama. Can you drive it? Sure - and it's worth a cheap less functional car if all you're doing is driving 10 miles to work and back 5 days a week. But when you start talking vacations in June or a commute to the city on a regular basis you're going to shell out the money and upgrade to something that's comfortable and suits your needs.

Lack of this feature will stop Wrike from being an Enterprise level project management tool. It's unavoidable that we're eventually going to have to upgrade to something better. Especially as Wrike continues to drive up it's price point while focusing on features that aren't going to make it appropriately competitive with comparably priced products.

Thank you for your additional feedback here Leann Lewis!

Per Ilia, Wrike's Product Manager, this improvement does not fit into this year’s roadmap due to other planned updates. We understand your disappointment, and the team will keep this suggestion on their radar. 

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

This would be helpful,  but I see it's been on here since 2017  and no comment that it's being worked.   I'll find my own work around I guess.