We've run into a couple of use cases requiring our users to implement shared work queues for teams that want to let users pick tasks they want to on. In other words, one queue needs to be fed tasks to be worked by the whole team. At this moment, K2 forces us to implement shared mailboxes which are not compatible with our Exchange configuration. From our view, it would make a lot of sense to separate the actual task/workload balancing from the actual configuration of the underlying infrastructure supporting cases/tasks. In other words, tasks may need to be picked via the mobile client or the workspace, not always depending on the email notification delivery. That dependency of email for tasks processing seems to be a bit old school considering the capabilities of mobile devices. To clarify, it's not the email based delivery of the task notification that's a problem. It is the requirement for having shared mailboxes.
It would be great if this dependency was removed in future versions of K2.
Our team has developed a workaround pattern around this product constraint however on the surface it seems that there should be an easier way to accomplish the same objective directly through product configuration. One could also dream about introducing additional work distribution methods to prevent task cherry picking from the shared work queue. i.e. first in, first out, priority based, etc.
Thanks!

Authors: Brenden Peterson, BJ Biernatowski