Wrike should distinguish between a projected milestone date and a confirmed date. When the date is projected, it should reschedule. This is how most good gantt charts function.
Yes! Would love to be able to reschedule milestones in gantt chart like normal tasks.
Milestones that are dependent should move to match the dependencies!!!
I agree with Matthew's original suggestion to have two different types of milestones, one that can be rescheduled and another one that can't. Sometimes my milestones are dictated by deadlines, in which case the current 'sticky' behaviour is perfect. However, most of my project's milestones are not driven by deadlines and I'd like to allow those milestones to re-schedule based on their dependencies.
This issue is not explained in the documentation about dependencies on the Gantt chart: https://help.wrike.com/hc/en-us/articles/209604229-Dependencies-on-the-Gantt-Chart-. Currently, it says, "When you reschedule a task with dependencies all dependent tasks are automatically rescheduled." A Milestone is a kind of task, isn't it? But Milestones are not automatically rescheduled when their preceding tasks are.
Have Wrike ever fedback on this?
I agree with Hans Juergen, actually you do need both. Sometimes you want the milestone to move along with its dependency, other times you do not.
Hey everyone, apologies for the delay in response here.
I have a quick update - it is possible to move tasks to reschedule tasks and their dependencies at the same time. If you shift+click on a task to move it, it moves the entire chain, including the dependencies. If you don't want to move dependencies, you can click without pressing shift and drag it to the new date. You can read more about this on our Help Centre.
Hope this helps! If you have any other questions, be sure to let me know.
Upvoted, need to be able to reschedule milestones as dates rollup on earlier tasks.
Thanks for supporting here @Nikita Gupta 👍
Very frustrating to have this lack of functionality. Forced to reconfirm all schedules and individually recalculate all rollups because of this.
Hello @Ed Kelley, welcome to the Community, and thank you for taking the time to share your feedback.
I do understand your frustration here and I've passed on your feedback to our Product team. I'll be sure to let you know if there are any changes in relation to this request. Please let me know if you have any questions.
Hi, adding support to this request. Has there been a way to resolve this?
Holding shift and moving tasks moves everything that has already been completed (shifts the entire timeline vs everything after the task that is shifting). Our deadlines move based on feedback from clients so if we receive feedback sooner or they are delayed we need to be able to adjust dates for the rest of the project timeline. Doing this manually is very tedious for large projects.
Agree with original poster that there should be 2 milestone types. Not having milestones who's dates update based on their dependencies limits the blueprint functionality quite enormously in addition to the communities concerns with managing projects where due dates are flexible targets not rigid deadlines. It gives me pause to have more than a few milestones in a project plan knowing I will have to update all of them every time a task completion date shifts...
Hey @Tyler Banschbach, thanks for sharing your input here. It's been noted and I've passed it on to our Product team.
Does Juan's suggestion above help at all? Also, welcome to the Community, it's great to see you here 🙂
I am having the same issue as mentioned in this thread. I'm confused on Wrike can be considered a serious project management tool without this basic function being available.
Hi @Chris Lau, welcome to the Community 👋
Thank you for your feedback! Our Product team is aware of this suggestion, and it would be great if you could upvote the original post above if you haven't yet as the votes help us gauge the interest for different ideas here in the forum 👍 Here's more info on our process.
For the curious, the workaround we did is similar to Juan's. I've set the "milestone" as a task but give it a duration as 1 minute and made "non-billable". Now the milestones (which are really tasks) adjust with dates.
Thanks for sharing @Adam Reusche!
Upvoted, we really need this!
Is there an update on this feature?
No updates currently, folks. Please be sure to upvote the original post at the top of the page if you haven't yet.
Its amazing how many standard gantt features you guys don't have updates on after years of requests.....It's really disappointing as a new user.
Agreed. Milestones should be able to be rescheduled based upon blueprint launch. Not having this feature creates extra steps that discourage use of the Gannt Chart within my team.
Hello 👋@Nico Wildeboer apologies for the delayed response! I understand your concern here. @Jadon Stanek, thanks for adding your support for this suggestion and for sharing your thoughts.I'll pass on both of your feedback to the relevant Product Team for their visibility. If I hear any updates in the future, I'll make sure to keep you posted. Thanks for your understanding.
Any updates on this from the Product Team? This creates a ton of extra work on our behalf. Going to try Adam's suggestion though to see if it helps.
Thanks for reaching out, @Tisha Redman. Our team is actively working on improving the Gantt Chart, but we don’t have a definite ETA at the moment. We’ll share an update as soon as we have more information.
Request for optional auto-rescheduling of milestones in Wrike A dependency should mean the same thing everywhere. Link a predecessor to a task and Wrike honours the logic. Link the same predecessor to a milestone and the date holds. The identical arrow on the identical Gantt chart means two different things, so users must remember which parts of their plan are live and which are decorative.
A milestone that cannot move cannot warn you. If a predecessor eight weeks upstream slips three weeks, the schedule already knows the gate will be missed. A fixed date suppresses exactly that information, if the milestone moves with the schedule this would be clearly evident using the updated Wrike baseline functionality. MS Project, Primavera P6, Smartsheet and numerous scheduling engines drive milestones off their predecessors, layering an optional deadline on top where the date is genuinely fixed. Manual upkeep drifts silently. Every slip means someone sweeping downstream milestones by hand, across every affected project. Across a portfolio of hundreds of gates that will fail, and nothing flags a stale milestone.
Wrike already has the dependency model, already reschedules dependent tasks, and already has auto-scheduling. The ask is the option of a per-milestone toggle with a project-level default: reschedule with predecessors, or hold fixed date. No new concepts, no migration.
One approach we've taken is to keep milestones as regular tasks and use a custom field to identify them as milestones. We also built an automation that alerts the right people whenever a "milestone" date is moved so it can be reviewed. It's not a perfect solution, but it's worked well for us as a temporary workaround.
Hi @Jason Selby, welcome to the Community! 👋 Thank you for taking the time to share your feedback and outline how optional auto-rescheduling could keep milestone dependencies consistent, highlight schedule delays, and reduce manual updates across projects. This is valuable context for our Product team. We’ll make sure your feedback is shared with them and keep you posted on any updates. Hi @Kelsey Rudolph, thank you for jumping in and sharing your workaround! Using regular tasks with a custom field and automation sounds like a helpful approach for teams facing the same challenge 😊
