issue tracker assignments

how are issues assigned?
updated by @blindmime: 03/25/16 10:26:13PM

How do you mean? Here at JR?


--
Paul Asher - JR Developer and System Import Specialist

I think I figured it out. I guess you would create a profile as your Issue Tracker profile and then assign that profile to the users you want to have access to those issues.

Let me know whats missing from the docs:

Docs: "Issue Tracker"
https://www.jamroom.net/the-jamroom-network/documentation/modules/2909/issue-tracker

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.

Nice one. I think private trackers is good. Use the forum to get all the detail which also included conversation and off topic discussion and different topics, then filter all that into a ticket that's easy to take action upon.

Sometimes there are issues that come up in the forum that will have sooooooo much information about different things that it becomes hard to understand what the issue is. Sometimes there are multiple issues, so the issue tracker being private is useful and productive.

What your doing does sound similar to what we're doing. Each of the 3rd party developers uses their own issue tracker here too, eg @ultrajam
https://www.jamroom.net/ultrajam/tracker

has their own tracker for their issues.

I must admit, I don't use that specific tracker as much as I could do.

But I use an entirely private tracker on localhost to keep me on track, and another on my dayjob site to let my immediate users know what I'm working on, and which of my bugs I already know of. They need to talk to me, email me or post to our forum and then I create a tracker bug, back burner or feature request as appropriate.

I really like that tracker, I use it every day and it helps keep my team productive and accountable


--
¯\_(ツ)_/¯ Education, learning resources, TEL, AR/VR/MR, CC licensed content, panoramas, interactive narrative, sectional modules (like jrDocs), lunch at Uni of Bristol. Get in touch if you share my current interests or can suggest better :)