|
2
2
|
Is it possible to make it so certain users can only see cases that are assigned to them? Or rather, I suppose another way of putting it is, can you make it so certain users are only associated with a specific case. This would mean that they can see the case no matter who it's currently assigned to, but it's the only case they can see in the project because it's the only case that they're associated with. |
|||
|
|
|
1
|
Our general stance in the past has been to trust the FogBugz user. Once you're inside the walls, we allow you to be segmented in to certain parts of the install, but when you can change something, you can change all of it. When you can see something, you can see all of it. This has helped to keep permissioning relatively simple (though it's still pretty complex). It's a trade-off we have made between simplicity and power. Is it absolutely the right way? Who knows? The only thing that's certain is that it's not an accident that FogBugz permissioning is relatively basic. |
|||
|
|
1
|
This level of detail in permissions is not currently available in FogBugz. If you need to restrict a user to only seeing cases he/she submitted, the best bet is to make them only a Community user. They would not be able to see and edit any cases, but they could submit new cases via email or a public project. Other users could work on the cases and reply by email and the community user could see the status and email history at the case status page. I have opened a case to evaluate the feature of per-user, per-case permissions. |
|||
|
