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

Allow Request Participants role / group to be added to Issue Security Schemes

XMLWordPrintable

    • 105
    • 4
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

       

      Update - 21st November 2024

      Hi everyone - we're current investigating this one.

      In the meantime, if you add 'Service Project Customer - Portal Access' to a security level, this will provide access to anyone in the 'Request Participants' field.

      Thanks, 

      Sam

      Summary

      When using issue security in a Service Desk project, Request Participants are unable to view the issue at all

      Environment

      Cloud
      Server

      Steps to Reproduce

      1. Create a new Service Desk project
      2. Create a new Issue Security Scheme
      3. Create a new ticket and assign it the Issue Security level in your Issue Security Scheme
      4. Add a second user as a Request Participant on the ticket that is not part of the Issue Security Scheme
      5. That user should receive an email
      6. Click on the link in the email

      Expected Results

      The user should be able to view the ticket they are a Request Participant on

      Actual Results

      The user can only see the main portal and not the issue he/she has been added as a Request Participant on

      Notes

      In this use case, it would be helpful if there was a way to add a Request Participants group / role to the Issue Security Scheme so that when people are invited to partake in a ticket, they are able to see the ticket within the Service Desk project.

      Workaround

      Create an Automation for Jira rule that looks for the Request Participants field to be updated. The action would be to Edit the issue to copy the value from Request Participants into a separate multi-user custom field. You can then use that field in your issue security and project permissions.

       

      Illustration

      Illustration of the requested solution

        1. image-2022-09-30-15-06-38-504.png
          331 kB
          Yuval Refaeli
        2. image-2024-11-21-09-02-58-006.png
          11 kB
          Sam Knight

              96677a1d9b4c Sam Knight
              mlavender mlavender (Inactive)
              Votes:
              200 Vote for this issue
              Watchers:
              104 Start watching this issue

                Created:
                Updated: