What can we help you with?

e.g. Gantt chart, Creating tasks, Sharing folders

More control with dependencies

32 comments

  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Joel Gold

    Iโ€™d like to take a moment to clarify this issue further, as there are several factors to be understood and considered regarding the dependancies shortcomings.

    The ability to:
    1. enforce hard dependencies (ie: prevent starting dependent successor tasks)
    2. filter out dependent successor tasks from dashboards (for example from a โ€œmy to-do list todayโ€ widget, if itโ€™s dependent itโ€™s not โ€œto-do todayโ€, regardless of the scheduled start date.
    3. filter out dependent successor tasks from โ€œmy workโ€
    4. prevent notifications in Wrike inbox when Iโ€™m assigned to tasks that are dependent on predecessors and not ready to be worked on.
    5. When a predecessor is completed, move the successor taskโ€™s start date to today maybe? For example if step 2 in a dependency chain was scheduled to take 3 weeks and it was actually finished early in 1 week (I know, miracles do happen, sometimes), in such a scenario, step 3 could start the day step 2 is completed, why does it stay scheduled to begin only in week 4?
    6. Overdue predecessors that are completed late creates a task that starts out overdue on the first day it can be worked on, this may be a unfortunate reality, but if Iโ€™m assigned to a dependent successor task and my teammate is late doing his previous step by 3 days, there is no way you can tell me Iโ€™m 3 days overdue on day 1 that I can start working.

    All of the above are real missing core feature.

    In our org we utilized the API to successfully solve 2, 5, & 6. And we are actively working on solving 1.

    3&4 cannot be adjusted via API. So we are stuck there unfortunately.

    Thank you

    Is this helpful? 2
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Scott Henderson

    Just to add to this very nice comprehensive list by Joel, a sister thread on dependency issues (https://help.wrike.com/hc/en-us/community/posts/115001633865-Automatic-Task-Status-Changed-on-Dependency-completion) points out (among other things) that there is also the problem of the product currently forcing us to set timelines in order to create dependencies (i.e. not allowing task dependencies without having to set task start and end dates) as well as the issue represented by the thread's title - not having the ability to automatically change following task statuses on dependency completions. IMO all of these issues should be considered by the Dev team together, not in isolation. I don't mean to suggest all of this needs to be solved in one rollout, but only that considering them together might allow for solving several of these in a combined manner, requiring less effort, and hopefully producing a smoother, less complicated final result. ๐Ÿ™‚

    Scott Henderson Arizona Community Foundation azfoundation.org

    Is this helpful? 0

Please sign in to leave a comment.

Folllowing List for Post: More control with dependencies
[this list is visible for admins and agents only]

Community

Welcome ๐Ÿ––

Hi there! ๐Ÿ™‚ Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome ๐Ÿ–– Have you checked out this week's Release Notes yet?

Hey! ๐Ÿ‘‹ Curious about something? Visit How To to search and ask the Community for answers.

Welcome! ๐Ÿ‘‹ Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.