issue tracker assignments
Using Jamroom
It seems clear to me. You've given a simple introduction behind how the module might be used.
I have a series of sites I'm developing which will be set up to provide support to various communities of users by a team of experts. I need a way to create Requests for the team to service.
The Issue Tracker and the Support Ticket modules provide similar functionality. I initially thought the Support Ticket module would work, but the Tracker's communication between the servicing team is better suited to my purpose. I believe I'm using it like you are using it at Jamroom, except community members will be creating the Trackers in my case.
I've also thought of using the two modules in tandem like Jamroom -- community members submit support requests or issues are raised in the forum and Team members create issue trackers as needed. But I'm currently thinking it's an extra step I can possibly bypass by letting the community instigate Trackers directly.
I may be wrong and it may turn out I'm weeding out more requests than I'd like. But right now I'm thinking it will provide a nice way to funnel all requests.
Just as you've mentioned in your docs that Jamroom Team issues are usually private, my issues will be mostly private between the team and the member who created the issue. I would rather Issues were private by default. I'm using it in communities of business managers whose issues will almost exclusively be private tasks they want performed.
At least that's the idea.
