Issue Summary

In Jira 5.12, a freely entered username that is an email address isn't accepted - only ones offered by the suggestion popup. However, with the Customer Permission set to Who can the issue be shared with? -> "Any customer, by typing an email address" The pop-up is not presented, and the customer should be able to enter a valid email address.

Steps to Reproduce

1. Setup a test JSM project. Username "admin" = Agent. Username "user" = Customer
2. Project Settings -> request Types -> Edit fields -> Add Request participants and Approves
3. Project Settings -> Customer Permissions:
   1. Who can raise requests? Customs who have an account on this Jira site
   2. Who can customers share requests with? Any customer, by typing an email address
4. Login as "user". In customer portal start to create a new ticket. Input username "admin" for both approvers and request participants
5. Click Create
6. Now as Admin, go and load the issue in agent view.

Expected Results

The username is listed in Request Participants and Approvers

Actual Results

Popup appears "the username cannot be found". The username can't be entered, and if the form is submit,the username entered won't be populated in the ticket

JSM 5.4:

JSM 5.12:

Workaround

It is possible to revert the change implemented somewhere between Jira 5.4 and 5.12 and revert the field back to text input with the dark feature sd.select.component.user.picker.uplift.disabled

1. Navigate to the URL <BASE_URL>/secure/admin/SiteDarkFeatures!default.jspa to go to the Dark Feature page
2. Enter sd.select.component.user.picker.uplift.disabled in the Enable dark feature section
3. Click on Add

Please note that all fields that are 'sd-request-participants' and 'multiuserpicker' will be displayed as plain-text input, so the usernames or email addresses will be case-sensitive.

Workaround 2

Changing the customer share permission to Any customer or organization by searching in this project will allow customers to use the new dropdown field and search for customer emails. But changing the permission will expose all customer emails in the search and can be considered a security issue depending on the use case; therefore, this is a bug.