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.

What can we help you with?

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

5 comments

  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Anastasia

    Hi Dru, great to hear from you again! :) Would love to learn a bit more about your request. Are you referring to dependencies based off of templates, or some preset dependency models? Looking forward to hearing from you!

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Dru Michaels

    Hi Anastasia,

    I would like to see, "with dependencies" added to the options provided when you duplicate a task .  Might be that is not advisable from a logic standpoint but if we are copying the tasks, seems like especially for those recurring projects, having the dependencies carry over would be ok.  However, I think at this point when you take a have tasks (within the project) in "ACTIVE" and add the dependencies and then convert the tasks to "ON HOLD" as recommended by Wrike's user doc says we should do for templates, that new status assigned "on hold" might wipe out the dependencies.  Would be nice though to be able to have the option to copy those dependencies over.  Thanks for considering.  

     

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Anastasia

    Hi Dru, thank you for following up! Since you're referring to those tasks which are set to a deferred status (for which it isn't possible to add a predecessor or successor task), it sounds like the concern might be that dependencies will disappear once a new status is assigned. I wanted to let you know that it's not the case, and that if the dependencies were set before task was updated to have a deferred status, those dependencies will stay in place, and dependencies will always be carried over to the duplicated Project. Is this what you were referring to? Let me know if I misunderstood!

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Dru Michaels

    Anastasia -

    Thanks so much.  I am so glad to hear that this was a case of user error :-). I have gone back and run thru a couple of typical duplicate--the-template scenarios and determined that I was mistaken.  Thanks so much for taking the time to assist.  On that note though, it would be great if the Template with tasks in "on hold" status, could be duplicated such that, the new copy would sustain the "on hold" status of those tasks vs instantly converting to ACTIVE.  Thanks so much for the help re: the dependencies staying in tact. :-)


    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Anastasia

    Dru, thank you for following up! I'm really happy to hear that helped. Let me know if you have any other questions! :)

    Is this helpful? 0
    Comment actions Permalink

Please sign in to leave a comment.

Folllowing List for Post: duplicating dependecies
[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.