-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
2
-
6
-
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?
- is related to
-
JSDSERVER-4310 Browse Users Permission Does Not Work For Customers in Service Desk Customer Portal
-
- Gathering Impact
-
- relates to
-
JSDSERVER-4765 Customers cannot search for users in the customer portal request forms via email address when customer permissions are restricted
-
- Closed
-
- links to
Form Name |
---|
Allow autofill in "User Picker" field without allowing request sharing
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
2
-
6
-
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?
- is related to
-
JSDSERVER-4310 Browse Users Permission Does Not Work For Customers in Service Desk Customer Portal
-
- Gathering Impact
-
- relates to
-
JSDSERVER-4765 Customers cannot search for users in the customer portal request forms via email address when customer permissions are restricted
-
- Closed
-
- links to