Wanted to get thoughts on if anyone has been able to configure permissions in next-gen SD. These are the two requirements my team needs in next-gen.
I have removed all group access to the project and just added project admins with custom built permissions. When filling out the form in the portal the user will be created as a customer. This testing worked, however some users are still able to see issues in the search function that are not part of the project admins added into the project.
Question: Is there a way to remove next gen SD tickets from being searchable by the organization? Or this is because the global permissions are setting the access/visibility into the project?
You can implement Issue Security Configuration setup against your project to fulfill your requirements. Take a look at this link - https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/
When issue security scheme is implemented, you can define different security levels and apply them against your issues. One of the usage is to restrict users can only see the issues that he/she reported in the project.
Hope this will give you a start.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Even though our Jira env is on-prems (Data Center), the concept of issue security should still work for Next Gen Projects in the Cloud env. The link reference that I provided is for the Cloud env and I don't see any mention of issues with Next Gen projects.
I would recommend you to submit a support request directly with Atlassian to ask them if there are any limitation with issue security scheme against Next Gen Projects.
Looking forward to hear what Atlassian has to say.
@Joseph Chung Yin Thanks so much for your insights. I was able to uncover that next-gen does not currently support ISC and by default any user who has a service desk license will be able to search for and view the tickets from the project. Looks like this is a feature request with Atlassian that has not yet been put on the roadmap :-(
For our use case, since we don't have enterprise so I can't spin up a separate instance to solve the issue, we will be migrating the project back to classic.
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events