We couldn't load the project sidebar. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 2
    • 6
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      When creating an approval flow, you often need to allow the customer to choose an approver from a list.  This is where the User Picker field comes in.  As the customer starts to type an approver's name in the field, the field autofills potential approvers' names.

      However, according to the JIRA Service Desk documentation, for the autofill to work, you have to allow customers to share their requests:

      "Before you begin, make sure your Customer permissions > Who can customers share request with? setting is on Any customer or organization, by searching in this project. This ensures that customers can search for approvers."

      https://confluence.atlassian.com/servicedeskcloud/setting-up-approvals-816880004.html

      In some environments, this is fine, but in ours, we really don't want customers sharing requests, since the requests have the potential of containing (somewhat) sensitive data.  Nonetheless, we would still like the User Picker field to still autofill.

      Could we get request-sharing permissions and User Picker autofill permissions separated so that they do not affect one another?

          Form Name

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • Icon: Suggestion Suggestion
              • Resolution: Unresolved
              • None
              • None
              • 2
              • 6
              • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

                When creating an approval flow, you often need to allow the customer to choose an approver from a list.  This is where the User Picker field comes in.  As the customer starts to type an approver's name in the field, the field autofills potential approvers' names.

                However, according to the JIRA Service Desk documentation, for the autofill to work, you have to allow customers to share their requests:

                "Before you begin, make sure your Customer permissions > Who can customers share request with? setting is on Any customer or organization, by searching in this project. This ensures that customers can search for approvers."

                https://confluence.atlassian.com/servicedeskcloud/setting-up-approvals-816880004.html

                In some environments, this is fine, but in ours, we really don't want customers sharing requests, since the requests have the potential of containing (somewhat) sensitive data.  Nonetheless, we would still like the User Picker field to still autofill.

                Could we get request-sharing permissions and User Picker autofill permissions separated so that they do not affect one another?

                        Unassigned Unassigned
                        4dae21178a5c Jason Freeman
                        Votes:
                        27 Vote for this issue
                        Watchers:
                        18 Start watching this issue

                          Created:
                          Updated:

                              Unassigned Unassigned
                              4dae21178a5c Jason Freeman
                              Votes:
                              27 Vote for this issue
                              Watchers:
                              18 Start watching this issue

                                Created:
                                Updated: