Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-10837

JSM permission validator asks to grant to "Service Project Customer - Portal Access" users all permissions including Assign and Delete

XMLWordPrintable

      Issue Summary

      JSM permission validator asks to grant to "Service Project Customer - Portal Access" users all permissions including Assign and Delete, even though they are not mandatory permissions.

      Steps to Reproduce

      1. Navigate to Jira Service Management Permission Scheme for a test Project
      2. Validate Assign/Delete Issues Permission is assigned to the Role Service Project Customer - Portal Access
      3. Remove either or both Assign/Delete Issues Permission per below screenshot
      4. Browse through the issue and navigate back to the Jira Service Management Permission Scheme for above test Project and we are presented with the Permission error below:

      Expected Results

      We should not have been presented with the Permission error

      Per below article, If you choose to use custom permission schemes, which are different from the mandatory permissions for the project roles in the typical service desk context then we will be presented with the Jira Service Management permission errors.

      This article lists the mandatory permissions for Service Desk Customers and below is the snippet for your quick reference:

      Service Desk Customers The permissions for customers must be granted to the Service Desk Customer - Portal Access security type, not the Service Desk Customers role. The Portal Access security type lets customers access the customer portal, but not Jira. The security type reads the role to determine who are customers. * Create Issues (Customers can create requests and view requests they have submitted via the customer portal)
      • Browse Projects (Customers can access the project in the customer portal)
      • Add Comments (Customers can comment on their requests.)
      • Create Attachments (Customers can add attachments to their requests)
      • Assign Issue (This permission is mandatory for the Assignee field to work. The Assignee field is an optional hidden field and it automatically channels issues to certain team members.)

      However, we see that Assign/Delete permission is not mandatory and we should not have got the error. 

      Actual Results

      We are presented with the Permission error below:

      Workaround

      We can just ignore this error and continue as currently there is no known workaround for this behavior. A workaround will be added here when available.

              Unassigned Unassigned
              ssamal@atlassian.com Shakti
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: