Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-5922

Removing the "Create Issues" permission for Customers prevents them from seeing requests in the portal

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 4.4.0
    • 3.12.2, 3.13.0, 3.14.0
    • Customer Portal

    Description

      Steps to Reproduce:

      1. Create a new basic Service Desk Project (using all the defaults provided in a fresh installation)
      2. Create a customer, and assign that customer to an organisation called "Everyone"
      3. As an Admin/Agent, create a request via the "Raise a Request" control on the sidebar (so the issue is visible in the portal)
      4. Once the issue has been created, share it with Everyone
      5. Log in as your Customer in a private window - verify they can see the request the agent created under "My Requests" when the "Created By" dropdown is set to "SHARED WITH MY ORGANISZATIONS" or "Everyone"
      6. As an Admin, Remove the "Create Issues" permission from "Service desk customer - portal access"
      7. As the customer, refresh the requests screen - and the request shared with the organisation is no longer visible.

      Use Case

      A customer might wish to use Service Desk for Announcements, and thus want a read-only-for-customers style desk, with which they can share requests with all customers. The need to have the "Create Issues" permission to simply view issues in a list seems incongruous and is confusing. Not having the "Create Issues" permission doesn't stop the Customer from viewing the issue directly - just from seeing it under "My Requests".

      Attachments

        Issue Links

          Activity

            People

              kkanojia Kunal Kanojia
              dnorton@atlassian.com Dave Norton
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync