We have contractors that work very collaboratively and help cover each other's tasks, and it would be great if they could all claim a task from a communal pool instead of transferring their tasks individually.
At the moment the only way to make a task available to everyone is for the task to be assigned to a user initially, then they unassign themselves. We have a lot of users and a lot of tasks daily, so for them to do this is very impractical. An admin creating or uploading the tasks as unassigned in the first place doesn't make them available to claim, only a user removing themselves does.
If this gap could be fixed, it would solve a lot of our problems and remove so many manual processes.
0
Comments
Post is closed for comments.
Hi Safe Seats Safe Kids!
Thanks for posting to the Community! We have definitely heard this request before and I believe you also found and commented on a post that has several upvotes already! To keep things consolidated and to know how much interest we have, we try to keep similar requests on one post so this post will be closed for comment. Thank you for giving that post your support through upvoting and commenting and I will be sure to pass this continued interest on to our Product team!
In the meantime, there is a slightly more specific instructions to the workaround I would like to suggest here and I will also update the other post with this information. In Mae's comment, she suggested, "dispatching the form to a designated user, such as yourself," and that is the correct workaround but additional clarification for this tip would be to always dispatch to yourself, or the admin/dispatcher who is managing dispatches, and then they need to open the dispatch on mobile, edit at least one field value, then "Save & Close" the submission to "activate" the submission on mobile. This is an important step for registering the dispatch as an active submission that can be claimed. Then using Work Hub, all dispatches can be unassigned as a bulk action to add them to the unassigned queue.
I recognize that this is a clunky solution which is why this request has been brought up before but I wanted to make sure that you might be able to use this tip in the interim. I also encourage you to reach out to our Product team via beta@gocanvas.com, they love hearing feedback directly from customers!