Issue Summary

When creating a remote issue link from Jira Cloud to a linked Jira DC instance (via Application Tunnel), the remote issue picker dropdown returns empty results. The picker passes the current Cloud project key as a context filter to the DC instance's /rest/remoteJiraIssueLink/1/remoteJira/picker endpoint. If the Cloud project key does not exist on DC, the search returns no results, and the dropdown appears empty.

Typing the full issue key (e.g., PROJ-123) and submitting works only affects the autocomplete/search dropdown.

Steps to Reproduce

1. Set up an Application Link between Jira Cloud and Jira DC using Application Tunnel
2. On Jira DC, open an issue in a project (e.g., project key TEST)
3. Click Link → select the linked DC instance as the remote server
4. Start typing in the issue search field to search for DC issues
5. Observe: the dropdown shows no results

Expected Results

The remote issue picker dropdown should return matching issues from the DC instance regardless of whether the current Cloud project key exists on DC. The Cloud project key should not be sent as a mandatory filter to the DC picker endpoint.

Actual Results

• The Jira DC picker forwards its currentJQL (for example, project = SC) to the
  linked Cloud instance. The Cloud search applies it as a mandatory filter, so an
  existing Cloud issue is excluded because it is not in Cloud project SC.
• Since project TETS does not exist on Cloud, the query returns empty results
• The dropdown shows nothing
• Typing the full issue key and submitting works correctly

Workaround

1. Go to Issues from the top navigation bar
2. Click Current search
3. Deselect any project that is currently selected/checked in the filters
4. Try the remote issue link search again. The dropdown will now populate correctly