[Functional Issue] Assignment and permissions (v 4)

[pk4]

We discovered the hard way yesterday that it is very easy to assign a task to someone who doesn't have permissions to view it. This creates an inconsistent situation where the person who assigned it sees the ticket as assigned, but the assignee doesn't see it at all.

To replicate:
1. Assume we have Worker A and Worker B. Ticket 1 is in Group 1, of which Worker A is a member, but Worker B is not
2. Suppose Worker A edits Ticket 1 and changes "Next Worker" to Worker B
3. From Worker A's view, Ticket 1 shows up in the assigned count (in the overview) and on any views of tickets assigned to Worker B. However Worker B will never see the ticket in their view of the assigned count, or in their assigned ticket view.

Possible Solutions:
A. It seems reasonable that if a ticket is assigned to you, that you should be able to view it regardless of the group it is placed in. However this may not be the easiest way to fix this.
B. An alternative fix would be to give a warning when you attempt to assign a ticket to someone who won't be able to access it. This fixes some of the problem, but it still leaves open the possibility that you could assign a ticket - and then subsequently move it to a location that the assignee can't see.

Comments?
Suggestions?

[joegeck]

This seems like a more than valid issue for usability. I posted it as is on our bug tracking site JIRA. No guarantees of a viable solution being implemented but the developers will evaluate it. Thanks!

http://www.wgmdev.com/jira/browse/CHD-689

[CWasko]

How about only showing a list of users that have permissions - this way there is no ambiguity?

[pk4]

How about only showing a list of users that have permissions - this way there is no ambiguity?

I'm assuming you mean to limit the "next worker" dropdown to the list of people who can actually see it.
This would be an improvement over the current situation, but it would still be possible to send a ticket into a black hole (by someone later moving the ticket into a different group).
If this is the approach taken, it could be helped by an additional warning if you try to move a ticket into a group where the assigned worker won't be able to see it.