
Комментарии
Kudos
Label | User name | User email | User type | Date | Link |
---|
Страница, которую вы ищете, не переведена, но у нас есть другие материалы на русском языке и служба поддержки на русском языке.
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!
More about Product FeedbackЧем мы можем помочь?
Learn. Share. Discuss.
Label | User name | User email | User type | Date | Link |
---|
I would very much like to be a part of this !
I agree, this is a feature present in most project management tools, and makes it a lot easier to split task in categories/phases/etc...
The point of the Sharepoint integration would be effectively that we can link Sharepoint documents in Wrike, so that the file is still hosted in Sharepoint, but we can interact with it as if it was...
For me, it's more of a visual thing. The card itself needs to be of a different color, or have some kind of bold colored line on the side. The goal is always the same : I need to know as much as po...
Yes it can work as a workaround, but a more practical solution would be great.
I agree, this would be a huge help. I'm currently doing a project with a few parents tasks, and a lot of subtasks, and the board is practicaly empty.
Could you please also remove my picture. Thank you.
We have the same issue : We use external IDs in custom fields, and we cannot search for them. This is a big issue for us.
Agreed, we could use this as well to mass edit custom fields. Though, copy/pasting whole columns from Excel to Wrike in Table view would help a lot in our usage scenario.
I agree, we could use that feature a lot. In our case, we do tasks for users requests that moves up one workflow, and related tasks for the actual software build that follows another workflow.