Steps to Reproduce:

1. Create a shared filter having similar JQL:

project in (PROJECT1, PROJECT2) ORDER BY created DESC

2. Login as a user having only browse permission for "PROJECT2".
3. View the filter in issue navigator.
4. It shows user the number of issues allowed to see. Add a "filter results" gadget on the dashboard.
5. Select the filter.

Result:

The user gets error message "The selected filter filter-<ID> has an error: A value with ID '<ID>' does not exist for the field 'project'..

Expected:

Here also user should be able to view issues from project having browse permission.

Update

The same happens when issue keys are specified in the filter query, but then the issues have a security level whose the login user does not have permissions on. In that case the issue key will be replaced by the issue ID in the search when opening the results, which breaks the search:

Issue does not exist or you do not have permission to see it.

Notes

Attempting to access the XML view of a filter with this configuration will result in a HTTP 400 with an error similar to "HTTP Status 400 - A value with ID '10000' does not exist for the field 'project'." as per the attached image.