Align the way Linked Issue field completes searches between global Issue Create screen and the Issue View

Issue Summary

Currently the way Linked Issues field search queries the backend for tickets differs between the Issue Create screen and the Issue View screen.

The issue this causes is the search on the Create Issue screen returns a narrower scope of tickets and may potentially not find tickets otherwise accessible when completing the same search via the Issue View on a ticket.

Steps to Reproduce

1. Create a ticket with the summary alpha on a project. In this example this creates issue key EXAMPLE-123
2. Click the Create button on the Jira UI again to open the global Issue Create screen and within the Linked Issues field search for either the key or the summary of the ticket created in the previous step
3. Create the ticket from the above step and navigate to it (ie EXAMPLE-124)
4. Within the ticket's Issue View, use the go to link ticket EXAMPLE-123 via the Linked Issues field by searching for the key or summary and the ticket will be found

Expected Results

The two fields behave in the same way and use the same backend arguments when making a search for tickets and the ticket is found in both based on a key or summary search.

Actual Results

The global Issue Create screen does not return the issue neither through the summary or issue key.

The issue is caused by different arguments being provided to the REST API. As an example, the given search term in this case is alpha.

Global Issue Create Screen:

https://example.atlassian.net/rest/api/2/issue/picker?currentProjectId=&showSubTaskParent=true&showSubTasks=true&currentIssueKey=&query=alpha

Issue View:

https://example.atlassian.net/rest/api/2/issue/picker?currentIssueKey=RH-7&showSubTasks=true&showSubTaskParent=true&query=alpha&currentJQL=project%20in%20projectsWhereUserHasPermission(%22Link%20Issues%22)%20AND%20(resolution%20%3D%20Unresolved%20or%20statusCategory%20!%3D%20Done)%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

The difference between the two calls is the Issue View REST API request has the additional argument currentJQL which returns the ticket in question.

Workaround

Entering the exact issue key in the global Issue Create screen can be used to link the ticket.