[Status: Backburner ⌛️] Tasks dependency setup should not be locked base on Task Status
Hi guys,
I noticed a strange behavior/UX in wrike today.
1- I was waiting for an information from some colleague, which blocked one of my task
>> action : task status = Blocked.
Then, having a bit of delay, i decided to create a specific task to get the action done by a colleague
2- Create second task, setup dependancy.
and here is the issue:
- if the task is "active", i can set the dependency
- if the task is "blocked" (on hold), I can't set the dependency
I do not understand this behavior. Whatever the actual status of my task, i should be able to manage all project management feature associated with those task, especially dependencies
read you soon and happy to get any feedback
Julien
hey Wrike Support team: quick up: is this a bug or on purpose?
thanks
I noticed this too while I was iterating a project template that we use. I had to change the parent tasks to an active status before it would let me assign dependencies. Looking forward hearing a response from Wrike on this.
Hey Wrike Moderation: a quick up?
Is this anoying behavior a bug or on purpose?
thanks
Julien
Hey guys, I'm very sorry for such a long reply, must have overlooked this thread 😔
@Julien, please let me know whether you've brought it up with our Support - if not, I can raise a ticket for you because I think this needs some troubleshooting.
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
Hey again, quick update: our Product team has plans to add this improvement to the roadmap for 2020. I'll let you know when I have more details. 😇
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
Hey everyone, there are still plans to implement this at some point this year. I'll let you know as soon as I have more information!
This would be awesome, as it's really not userfriendly, costs some time, and generates useless notififcations, so bring sometimes confusion.
Looking forward for a positive bug fixing and thanks for the information
Hello, I see this issue is still on Backburner. We could REALLY use this addition, otherwise we have to set them to Not Started, but they are actually just waiting on someone else to finish a task before they can begin. Then they show up as Overdue which is not the case, and can get cluttered with the rest of the Overdue items that are actionable.
Any word for the On Hold dependency capability?
Hi Stacey Olsen, thanks for checking in here.
Looking into this for you now and will be back here ASAP 👍
Elaine Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Elaine Wrike Team member Become a Wrike expert with Wrike Discover