
コメント
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 FeedbackWrike のサポートページをお役立てください
Learn. Share. Discuss.
Label | User name | User email | User type | Date | Link |
---|
Please include me in this beta. Thank you.
I agree, it's definitely a blind spot in terms of functionality. I've brought it up multiple times and I always get the answer to just add the project name as a prefix. It's not ideal and a more ma...
I agree there are opportunities for improvement here. What we currently do as an organization is we prefix the task name with the project name so it looks like this "Project #1 - Task #1". It's s...
Hi @Nicole Bechard, My PMO is working to move people away from manual reporting on projects using Excel or PowerPoint and introduce Wrike Analyze into more of our regular project reporting. We were...
Agreed, this would be incredibly useful for seeing dependency chains in our projects.
This would be very helpful.
Congrats to all!
This is fantastic news Hugh, thank you for the update. I am assuming that we will have the ability to control who can delete the fields by customizing access roles, correct?
This disappointing decision significantly reduces the usefulness of the blueprints section in Wrike. Any serious project planning will have to be done in the production environment so we can set pe...
I'm glad I'm not the only person who is irritated by this. When something is set up or configured in the blueprint section those same settings should be carried over when it becomes a live project....