
It looks like we don't have the translated page you're looking for, but we do have other content in English and offer support in English.
It looks like you're trying to figure something out.
Stuck or just want advice?
You can unlock the true value of Wrike in our Community
Connect with thousands of leading teams, learn best practices, and shape the future of the product. What are you waiting for?
Now other members can find, vote, and discuss your idea.
Our Community Team reads every suggestion (yes, every one) then compiles and shares the feedback with our Product Team. Happy posting!
What can we help you with?
Learn. Share. Discuss.
In our use case, we have hundreds of projects to coordinate (as we use this as a customer work queue to build and install customers). Every "project" has the same 20 tasks, or so, and those 20 task...
Instead of a push of the custom field down into subordinate tasks or subtasks, you could place the custom field into a unique variable and expose the variable to the users so we can then reference ...
Definitely needed!
We would love to see this feature
Absolutely!
This is an important step and seems easy to implement. Wrike already posts a note in the stream when the task is complete, it is aware of dependencies and predecessors and should easily be able to...