Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-8317 Team-managed Jira Service Desk Projects
  3. JSDCLOUD-9109

Ability to Create the Service Desk Customer role in Team-managed projects

XMLWordPrintable

      Issue Summary

      Now that customer permissions are exclusively on the customers tab, there is no way to automate provisioning of customers with Atlassian Access for closed help desks using provisioned groups, a workaround exists but the portal-only users who are also Jira Software users will still be capable of seeing all issues internally, even not reported by them.

      In cases that the users are agents for other Service Desk projects, that will give them power to edit the issues from projects they should only be customers.

      Workaround

      https://community.atlassian.com/t5/Jira-Service-Desk-articles/Creating-the-Service-Desk-Customer-role-on-Next-Gen-for/ba-p/1363580#M279

      There is another workaround to achieve this using REST API: https://confluence.atlassian.com/jirakb/add-a-group-to-service-desk-customer-role-in-a-team-managed-jsm-project-1235851188.html 

      Suggestion

      Create a role that has special permissions for portal-only usage or improve the customers tab to accept Jira groups.

            [JSDCLOUD-9109] Ability to Create the Service Desk Customer role in Team-managed projects

            Christopher made changes -
            Component/s New: Permissions & Roles - Agents, Core & Software Users [ 63694 ]
            Jehan Gonsalkorale made changes -
            Assignee Original: Gabriel Raubenheimer [ ed36d73f045d ] New: Rachel Crossman [ rcrossman@atlassian.com ]
            Jehan Gonsalkorale made changes -
            Assignee New: Gabriel Raubenheimer [ ed36d73f045d ]
            Tyler B [Atlassian] made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 764763 ]
            Swati Kahol made changes -
            Description Original: h3. Issue Summary

            Now that customer permissions are exclusively on the customers tab, there is no way to automate provisioning of customers with Atlassian Access for closed help desks using provisioned groups, a workaround exists but the portal-only users who are also Jira Software users will still be capable of seeing all issues internally, even not reported by them.

            In cases that the users are agents for other Service Desk projects, that will give them power to edit the issues from projects they should only be customers.

            h3. Workaround

            [https://community.atlassian.com/t5/Jira-Service-Desk-articles/Creating-the-Service-Desk-Customer-role-on-Next-Gen-for/ba-p/1363580#M279]
            h3. Suggestion

            Create a role that has special permissions for portal-only usage or improve the customers tab to accept Jira groups.             		New: h3. Issue Summary

            Now that customer permissions are exclusively on the customers tab, there is no way to automate provisioning of customers with Atlassian Access for closed help desks using provisioned groups, a workaround exists but the portal-only users who are also Jira Software users will still be capable of seeing all issues internally, even not reported by them.

            In cases that the users are agents for other Service Desk projects, that will give them power to edit the issues from projects they should only be customers.
            h3. Workaround

            [https://community.atlassian.com/t5/Jira-Service-Desk-articles/Creating-the-Service-Desk-Customer-role-on-Next-Gen-for/ba-p/1363580#M279]

            There is another workaround to achieve this using REST API: [https://confluence.atlassian.com/jirakb/add-a-group-to-service-desk-customer-role-in-a-team-managed-jsm-project-1235851188.html] 
            h3. Suggestion

            Create a role that has special permissions for portal-only usage or improve the customers tab to accept Jira groups.
            Swati Kahol made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 760618 ]
            Victor Romero made changes -
            Summary Original: Ability to Create the Service Desk Customer role for Team-managed projects New: Ability to Create the Service Desk Customer role in Team-managed projects
            Victor Romero made changes -
            Summary Original: Create the Service Desk Customer role for Next-Gen New: Ability to Create the Service Desk Customer role for Team-managed projects
            Rodrigo B. made changes -
            Parent New: JSDCLOUD-8317 [ 1291680 ]
            Workflow Original: JAC Suggestion Workflow 3 [ 3872569 ] New: JAC Sub-task Workflow [ 3875937 ]
            Issue Type Original: Suggestion [ 10000 ] New: Sub-task [ 6 ]
            Status Original: Gathering Interest [ 11772 ] New: Open [ 1 ]
            Rodrigo B. made changes -
            Description Original: h3. Issue Summary

            Now that customer permissions are exclusively on the customers tab, there is no way to automate provisioning of customers with Atlassian Access for closed help desks using provisioned groups, a workaround exists but the portal-only users who are also Jira Software users will still be capable of seeing all issues internally, even not reported by them.
            h3. Workaround

            [https://community.atlassian.com/t5/Jira-Service-Desk-articles/Creating-the-Service-Desk-Customer-role-on-Next-Gen-for/ba-p/1363580#M279]
            h3. Suggestion

            Create a role that has special permissions for portal-only usage or improve the customers tab to accept Jira groups.             		New: h3. Issue Summary

            Now that customer permissions are exclusively on the customers tab, there is no way to automate provisioning of customers with Atlassian Access for closed help desks using provisioned groups, a workaround exists but the portal-only users who are also Jira Software users will still be capable of seeing all issues internally, even not reported by them.

            In cases that the users are agents for other Service Desk projects, that will give them power to edit the issues from projects they should only be customers.

            h3. Workaround

            [https://community.atlassian.com/t5/Jira-Service-Desk-articles/Creating-the-Service-Desk-Customer-role-on-Next-Gen-for/ba-p/1363580#M279]
            h3. Suggestion

            Create a role that has special permissions for portal-only usage or improve the customers tab to accept Jira groups.

              rcrossman@atlassian.com Rachel Crossman (Inactive)
              rbecker Rodrigo B.
              Votes:
              37 Vote for this issue
              Watchers:
              27 Start watching this issue

                Created:
                Updated: