Should be able to set start date without a due date (and vice versa).

Thank you for reaching out and sharing your feedback Ellen Nunes! I'm passing it on to the team, and I'd also like to mention a couple of things that are currently available that might be helpful in the meantime. First of all, it's possible to only have a due date for a task - such tasks are called milestones:

They can be turned into regular tasks when needed too.

It's also possible to create backlogged tasks with no dates at all. Can you please let me know if you're using these options, or whether they are helpful in your case? 

Lisa Community Team at Wrike Wrike Product Manager Werde ein Wrike-Experte mit Wrike Discover

Lisa Wrike Team member Werde ein Wrike-Experte mit Wrike Discover

Thanks for the reply Lisa. Yes I'm aware of those options, but the use cases I described are tasks not milestones, and the work is current not backlogged. So those options would create additional work and/or problems with visibility for us.

Thank you for clarifying Ellen Nunes! Your feedback has been passed on to the Product team 👍

Lisa Community Team at Wrike Wrike Product Manager Werde ein Wrike-Experte mit Wrike Discover

Lisa Wrike Team member Werde ein Wrike-Experte mit Wrike Discover

+1

Thanks for supporting this suggestion Kelly-Anne Slatton! 

Lisa Community Team at Wrike Wrike Product Manager Werde ein Wrike-Experte mit Wrike Discover

Lisa Wrike Team member Werde ein Wrike-Experte mit Wrike Discover

+1

+1

+1

We got the same issue, thx.

Hi folks! Thank you for your continued support here! Please don't forget to upvote the original post by Ellen here as well:

Lisa Community Team at Wrike Wrike Product Manager Werde ein Wrike-Experte mit Wrike Discover

Lisa Wrike Team member Werde ein Wrike-Experte mit Wrike Discover

Hi Lisa - have there been developments here at all? Thanks.

Hi Sergey Lyakh 🙋🏻‍♀️

Thanks for checking in. At the moment, you can set a start date without a due date, or a due date without a start date, for Projects and Project-based CITs from the Table View. However, this option isn't available for tasks. I'd love to hear about your specific use case. Thank you! 👍🏽

Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Werden Sie ein Wrike-Experte mit Wrike Discover

Basudha Sakshyarika Wrike Team member Werden Sie ein Wrike-Experte mit Wrike Discover

Hi Basudha Sakshyarika, 
Our use case is similar to that of the OP: 
• We should be able to set a start date without an end date (when the beginning of the work is known but the size and/or resource availability is not)

Sometimes we have requests coming in as tasks, and the start date is how we can plan them out. But we don't always know ahead of time how long they will take.

Also, when I'm setting the dates, I would sometimes enter the ones I know and then fill in the blanks later. But since it forces a duration, it's hard to tell which dates I intentionally entered and which were auto-generated.

As for why we need this on tasks in addition to projects:
If trying to filter for both tasks and projects, a lot of extra noise is shown, so I've been primarily working with tasks → filtering just for tasks and applying the "Subitems: Single list of tasks" view.

I would love to see this as well:
• We should be able to set a start date without an end date (when the beginning of the work is known but the size and/or resource availability is not)

Our main use case that brought me to this thread is that we're using Wrike to create a list of issues for a major project we just went live with. We know the start date (which we use as the date the issue was raised), however we don't know the end date yet, as that will depend on the priority of the issue and any other issues that may arise.

Hi 👋

Sergey Lyakh, I'm stepping in for Basudha, and I apologize for the delayed response. Thank you for taking the time to share your use case with us. I understand how this could benefit you. Sharon Ziska, thank you as well for sharing your feedback, use case, and for supporting Ellen’s suggestion.

Please upvote the post if you haven’t already, as this will help us consult with the Product Team and assign a relevant status once the post receives 60 upvotes. For now, I have forwarded your comments to the responsible team. If there are any developments in the future, we’ll post an update here.

Rohan V Community Team at Wrike Wrike Product Manager Werden Sie ein Wrike-Experte mit Wrike Discover

Rohan V Wrike Team member Werden Sie ein Wrike-Experte mit Wrike Discover

We are utilizing a blue print for request form submissions that contains the tasks that will be required. These tasks must be done in a particular order (so we would like to set up the dependencies via the blueprint), but the duration will vary depending on the unique project requirements. Setting the dependencies automatically sets the dates.

Only after the project is reviewed and approved by the internal team, would we want the first task in the request to have a start date (the date the request was approved), however we would not want dates on any of the other tasks until the task they are dependent on has been completed. 

It would be great if we could set a dependency without dates, and not have the system automatically generate an end date when a start date is added.

Hi, Ashley Fischer 🙋‍♂️ thanks for explaining your process clearly! We’ll keep you posted if there are any updates 👍

Rohan V Community Team at Wrike Wrike Product Manager Werden Sie ein Wrike-Experte mit Wrike Discover

Rohan V Wrike Team member Werden Sie ein Wrike-Experte mit Wrike Discover