Lack of query revalidation for saved filters in Issue Navigator leads to unexplained empty query result

Reproduction sequence:
1. Pick up an issue that is visible to user 1 and not visible to user 2. Let's say it has ID 10111.
2. User 1 creates saved filter issue = 10111 and shares with user 2.
3. User 2 opens the saved filter.

Obsreved: no errors, no result.
Expected: error message that issue does not exist.

The expectation is set by the case when issue key is used instead of issue ID.

Speculation:
As with JRA-32772, this is because if query string equals saved filter string, it is not validated (DefaultIssueTableService.getIssueTable()). Here, after sanitization the query remains the same, and is not validated.