Question

Community users are usually the worst at logging bugs effectively - therefore a way of communicating issues about a particular case would be extremely useful.

Answer 1

Community Users cannot be assigned cases in FogBugz (only normal, administrator, and virtual users can be assigned cases). Instead, when a community user files a case their email address is set to be the correspondent for that case.

We use the same workflow for cases emailed into us by customers as we do for community users, which is roughly:

1. When a case comes in, if further detail is required we just click "Email" or "Reply" on the case in question. This uses the correspondent field to know who to send the email to.
2. After sending an email asking for more details/clarification/etc., we resolve and close the case as "Resolved(Responded)". This way, if/when the community user replies to our email, the case will be re-activated in FogBugz and assigned to the person who closed it (i.e., me). I will then receive a notification about the incoming email/case reactivation and can continue working on the case.
3. Repeat steps 1 and 2 as necessary when interacting with the community user.

We find this workflow works nicely as it still allows us to assign the case to other (non-community) FogBugz users when necessary, have private dialog within the case that is not exposed to the community user (e.g., discussion of code changes), etc.

Admittedly this workflow doesn't work for everyone. If you don't think it will work for you and your team, can you provide us more detail of what workflow you'd like to see?