[Status: Backburner ⌛️]Adding Dependencies to tasks with no Date field
I don't know how much of a common need this is for other people but I feel the ability to add dependency to a task without specifying a certain date would be nice. Some of my company's projects happen quite fast and sometimes it is hard to give firm dates on when certain tasks should be done. However it would be nice to still be able to set dependencies on tasks to indicate to my Project Management Team that one task should come before another. In other words, I need to indicate that a Project Manager can't complete a certain task without the completion of the other, without auto generating completion dates for those tasks.
Of course you can give temporary dates for each task when making dependencies but those date are most likely incorrect and indicate that we have a bunch of incomplete tasks when in all actuality that task might not even be started yet. When scanning over statistics for all projects this could be a little misleading.
If this is completely outside the scope of the product I completely understand. It was just a thought. Thanks!
➕➕
Thank you for adding your support Jules Bowie 🙌🏼
Hi, I would like to add to this request by allowing dependencies to exist in the template without dates set. When I use a template with dependencies, there are dates set so that the dependencies are created automatically. Having false dates shows the project in the red and also does not offer clarity as to which dates are accurate, when implementing the real dates. On large projects, and with many projects being launched at the same time, this becomes tedious and hard to follow/manage. The relation between dates and dependencies is a huge problem. Hopefully Wrike fixes this so we can actually plan projects in advance or on the fly when there are tight timelines. Come on Wrike! The first post on this request was in 2017!
Hi Marta Stanis, welcome to the Community 🤗
Thanks a lot for supporting this idea and sharing your use case here! 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
Sad to see this is on the backburner, my team could definitely use this!
I'm very disappointed to see this is on back-burner. Wrike is a project management tool. Having dependencies without setting dates is crucial to most project planning and critical for my team. This is super frustrating.
Does the backburner mean it's closer to being worked on, or is that more of a permanent hiatus thing? I'm also hoping this gets moved to the forefront sooner rather than later. We've already been waiting 5 years 😂
Hi everyone!
The Backburner status means that the team sees how this suggestion would be useful and would like to get back to it when they can. That's why we keep passing on the new feedback here, and once we have an update from the team, we'll make sure to let you know.
Thank you for your continued support here!
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
Yes, this is something I find myself needing on a regular basis when creating templates to be duplicated.
One thing specifically we need "no-date-dependencies" for is onboarding. We have created a task for onboarding with many subtasks related. In the onboarding process there are items that are essential to come first before any others, thus creating the need for dependencies. However, we don't always know when the background check of an employee might end, thus allowing us to move forward. Because of this, the automated dates shown when adding a dependency create an issue and a false timeline of the main tasks and subsequent subtasks.
Hi Jessica Huffman, welcome to the Community! Thank you for sharing your use case here, I've passed on your feedback to our Product team👍🏼
Just here to follow this conversation, as I would find this very useful.
Hi June Dzialo, welcome to the Community 🙂
Thanks 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 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
Sigh, add one more to the pile. It is a big limitation for us that dependencies can only exist when there are dates assigned.
Hi Matt Snyder, welcome to the Community, and thank you for taking the time to share your feedback. The team is aware of the request here, and we'll be sure to let you know if there are any updates👍🏼
This is a huge pain point for my team. We have automations that rely task dependencies, and dependencies getting cleared when our PM removed the dates is very disruptive to our workflow.
Why is this not a priority for Wrike? This is Project Management BASICS! Dependencies do not and should NOT rely on dates. Your dev team needs to figure this out. How is Wrike even being considered a PM tool without a top 3 functionality?
Hi everyone! Please rest assured that all your feedback is passed on to the team and this suggestion, being one of the most popular on the Community. For now, the team is focused on other priorities, so there is no scope to add this feature to the roadmap at the moment. As outlined in this Community post, the Product team looks at a wide range of data, user feedback, and Community suggestions/votes to determine what next to work on. The team always aims to focus on implementing the functionality that will have the widest impact and benefit for the most users, and it's for this reason, that we simply can't implement all of the suggestions we receive via our various feedback channels.
Having mentioned all of that, we still understand this is a highly sought-after functionality among some of our customers. We'll continue to share your feedback with the team and if there are any changes to this, we'll be sure to let you know.
Related question, is there a way to add dependencies but not change the dates? I don't want it to auto assign the dates, I have the project laid out already.
I've been watching and waiting for this feature for years now - officially adding my voice to this request.
Thank you for your continued support here, folks!
James McNicholas I've asked my colleagues from the Support team to reach out to you about your question, and I can see they have 👍
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
5 years in and still waiting for this functionality to be enabled? The original table view is great, so I'm disappointed all efforts have apparently been focused on the new table view (which seems like a mostly cosmetic update) while important functionality like this is overlooked.
Amen Melissa
This is probably the biggest flaw Wrike has. Dependencies with mandatory dates is ridiculous. This is supposed to be a premium project tool.
Thank you for sharing your feedback here, folks! We will let you know if there are any changes planned here.
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
As a new Wrike user, I am setting up my team's workflows and trying to find the limitations of the software. This is a major one. Many of our tasks are fluid in duration but have a definite dependency structure. Not being able to have date flexibility is a real annoyance. It is not reassuring that this has been a request for six years and that the most substantive reply has been that Wrike was not coded to work in this way. Instead of "backburner" status for years on end, it would be more reassuring to let us know if or when a major code rewrite for this issue is planned.
Brian Crawford amen. We generally like the tool, but this is one of the biggest gaps and has a noticeable negative impact on our projects.
Please, rest assured that the status assigned to this idea is accurate: even though we don't have an ETA to provide you with, the Product Team is interested in the idea and if there are any changes to the status here we'll be sure to let you know.
Why would adding a date when simply adding a task dependency be automatic and mandatory? Very poor design!
We ask for due date options in request forms, but can't get them.
We don't want dates automatically added when creating task dependencies, but you won't turn them off.
Seems like it should be a minor change to turn off unwanted auto-dating when creating a task dependency.
Thanks a lot for adding your support for this suggestion Kevin Austin. We will let you know if there are any changes here in the future.
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 Lisa,
I'll be also a lot interested in this features! I'll spoke about that with my Wrike seller. I need a workaround for my templates