I understand the process for adding a user to an issue but is there a way to set that for anyone within a client org to see all of their open tickets? For instance if we have a client and we give access to the portal to 5 of their administrators can we set it so that by default any of those 5 can see any tickets (issue) that were created by any of the other people from that same client? Basically what I want to accomplish is to allow anyone from a specific client to see any service request that is related to their company. Right now the only way to do this is for the creator to manually add all of their peers (other administrators) onto any issue that he or she has created. I want to prevent duplicate issues from being created by a client and make it easier for them to work their collective issues.
A relatively simple and self service way to accomplish this is to allow a customer to add people to a ticket and then offer an option for that person to be saved and added to all future tickets. Basically let the customer create his "team" either all at once or over time. Then the customer could pull up his profile and see "My Requests" or My Team's Requests." Add People to a Team.png
Hello, I am trying to do the same thing - allow a group of customers to see each other's tickets. Is there a way of doing this with customer groups so it happens automatically? Requiring customers to add everyone on their end isn't a solution that will work for us. And on the agent side, the agent isn't sure who all should be added. We just need to be able to have a group of customers see all the tickets created by that group.
Sam, if you just want anyone to be able to see the tickets in a project, you can set the 'Browse Project' permission for that project to 'Group (Anyone)'. I've never tried this for a Service Desk project, and there are a lot of obscure restrictions around Service Desk permission schemes, so I wouldn't be surprised if it didn't work, but it's definitely worth a shot if this is your goal. If it does work, then anyone who could access your JIRA server would be able to see tickets in that project through the standard JIRA GUI. This may complicate things as your customers would then be able to access tickets they reported through both the Service Desk portal and through the standard JIRA interface. If you're using automated transitions, then this can lead to some broken automation depending on whether a customer comments on a ticket through the portal or through the JIRA GUI.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot