[Status: Launched! 🚀] Setting permissions on who can mark a task or project to COMPLETE.
It would be very helpful if there was a way for the creators of a task or project to prevent people from changing the status to complete. It should be something as simple as either the creator ONLY can mark something as complete or both can.
As a supervisor, it gets hard to track what needs to be looked over when people can just mark the task/project as complete.
We tell the staff to mark it "In review" but this is not a sure thing...I would like to limi that so it's clear on my dashboard what is in review so I can mark it as complete when it's looked over.
There are some tasks that I would allow them to mark it as complete if it's a small task but I want the choice.
Hi @George, thanks for sharing feedback and giving details about your use case.
This is also something my company would like to have. A way of Preventing Collaborators from changing workflow status
@Larry, thank you for your input! :)
This is something that would be usefully for our team as well.
Would be very useful indeed!
I think that Wrike either needs a «Client»-permission-level below Colloborators, with clients not being able to see hours worked (basically the whole «update»-stream should be invisible to them, not being able to move tasks etc. Uploads, Comments, seeing what happens, filling out request-forms, maybe starting tasks manually in the inbox but that's it. I can't have a client seeing who works when for how long on his project, that is first and foremost internal information. Other solutions handle this better (as, frankly, the whole time-tracking needs a bit of work ;-)).
As the many possibilities to include clients (PDF-review etc) are one of the best arguments to use Wrike, this is really important. Either a «client»-level below «Collab», which should be easy enough to implement... or - a bit more complicated but in the end it would be the better solution – being able in the user management section to exactly decide what a member of the team, a collab or a client can or cannot see, as this would enable us to specify with external clients to have some «leaing» a project on their side and others just being more passive onlookers. Frankly, this is what kept us from using Wrike (some other stuff as well, but the visible Timetracking broke the horses back in a MASSIVE way ;-)
This goes a bit beyond what is discussed here, but as I am sure every company has different needs, the ability to fine-tune user permissions should be interesting for Wrike.
Otherwise, lots of great potential and maybe one of the finest Projectmanagement apps I've encountered so far.
Thanks for sharing your thoughts about user licenses and permissions! I really appreciate the details, they definitely help understand how the ability to have even more granular controls could benefit teams with different use cases, such as what you've described. Our Product Team is always interested in learning about different workflows and scenarios, and I'll make sure to point this comment out. Thanks again for sharing!
Hi - my pleasure, it would be cool if something like this would come as it basically kills Wrike for us.
(Plus, Time-Tracking could be improved a bit, sometimes by small details like enabling the Kanban-«Cards» to start the clock without having to open the Taskdetails (little clock-icon). And, hourly rates,flatrates etc. Take a look at how Active Collab and Paymo do this. Wrike sure outoperforms these platfoms in other aspects, but Paymo is utterly smart about getting your time measured. It should be easy, maybe even toyetic and fun to get this done, as everybody hates time logging when you're in the flow of work.
If I can help you in any way with input, let me know.
Thanks for the reply! We'll definitely get in touch here if our Product Team has follow up questions. :)
Yes! Definitely this.
I've had jobs marked as Completed be changed to New by a Collaborator a few times.
I love the Collaborators feature but I would love it even more if only a Regular User or Admin could change the Workflow status.
@Eric, thanks for commenting and weighing in on this! If you haven't already, make sure to click the "+" under the original post to add your vote to it too. :)
This is a MUST-HAVE Feature and for me is a potential deal-breaker for using Wrike as a PM. I've just discovered a bunch of tasks were marked complete by a collaborator that weren't complete and it's messing up my whole project!
Please implement this URGENTLY.
Hi Paul, thank you for adding how this affects you. Even though I don't have a solution available with the current functionality, I understand how frustrating something like this can be. I can suggest some potential options for reviewing changes (Dashboards and following tasks) so that you can try and catch mistakes like that?
Stephanie thanks for this but I'm losing all control of my projects when collaborators can do this. This is project management 101 stuff.
If I'd known about this huge weakness in Wrike, I would not have purchased it.
Who do I speak to about cancelling my subscription and getting a refund?
Hi Paul, I'm sorry to hear that. I've asked your Account Executive Peter to reach out so that you can discuss your plan. If there's anything I can do to help in the meantime please let me know.
This just happened to me again. A Collaborator marked a task as complete. This needs to be fixed ASAP.
I'd like to say that for my company it is also "a potential deal-breaker", like Paul said recently.
We need to control collaborators possibilities in changing statuses.
It's kinda sad that nothing changed in this side of Wrike since December 29, 2016 19:09.
This assignee should be able to mark the task as "Pending Completion".
The assignor should be able to convert it to "Fully Complete".
This needs to be part of the mandatory workflow.
The assignee should not be able to bypass.
Optionally, the assignor should be able to checkbox whether or not they want the assignee to be able to Fully Complete without further review.
I could use this feature - not so much for collaborators - but for our internal team as well.
Stacey Gill Munich Re
A 'read only' permission setting in the share settings for a folder or project would be a useful addition and could address some of the issues set out above. Being able to restrict what can and cant be done and varying it for individuals or groups, as opposed to a users account type, across projects and work folders would be ideal.
We are using Wrike to interact with others outside of our organization. When we hit them with a subtask it would be nice if they only had a few options to select rather than the entire list of 60 custom workflows
Has this issue been solved or will be shortly? I am looking at purchasing a PM tool and tried Wrike for a week now. It is already driving me mad that team members can change the status of a task as complete when it's not, meaning I constantly have to check and update tasks' status again!
That is good news! Could you include the link to the Help Center article. The link in your post is not working.
Whilst I think this update will help some it still does not restrict things to a level that I would need sadly. Although you now can monitor who has changed a status it does not prevent dates being changed or any other critical path info being changed and even if it did someone still has to go back and re-open/reset the tasks. A simple read-only permission would solve this completely. Sadly, for me at least, your solution doesn't resolve the problem!
The new update if a terrible solution to the issue or preventing status being changed by assignees.
You have shifted the responsibility now to the ASSIGNOR who must monitor EVERY change in status to find the one that should not have been changed.
Please just simply allow assignors to OPTIONALLY:
a) prohibit assignees from changing status.
b) create a new status called, "PENDING COMPLETION"
It's really that simple!
The new option helps a lot in some cases and is a step in the right direction, thank you for that!
Are there plans to allow this on a folder level too? Right now we can only set somebody being responsible for a status change for all project/folders using that status. But depending on which department or e.g. under which project leader the status change was made another person is responsible and it does not make sense to copy the custom statuses x times just to have an own version for each department or project leader.
Hi Beat, right now we don't have assignees for Folders, would you like to be able to assign someone to the overall Folder itself (similar to how you can have a Project owner)?