GraphQL Query Issues does not work with Service Account Tokens
Summary
When using a Service Account token to trigger the GraphQL issues queue, it returns empty (no failures or errors).
Triggering the same query with another user's token (for example, admin token) returns correct data.
Note: The GraphQL Issues Query is experimental but I believe that Service Account tokens are not behaving intuitively for other functions as well (see related issue #432515 (closed)).
Steps to reproduce
On a self-managed instance, use the following query:
curl -X POST -H "Content-Type: application/json" -H "Authorization: Bearer <TOKEN>" -d '{"query": "query { issues(assigneeUsernames: [\"<ASSIGNEE_USERNAME>\"], state: opened) { nodes { title, webUrl } } }"}' https://gitlab.example.com/api/graphql
Notice that other Personal Access Tokens have results while Service Account Tokens produce no results.
Example Project
Tested on a self-managed v16.3.6 instance but could affect SaaS as well.
What is the current bug behavior?
Service Account tokens do not produce expected results when executing this query.
What is the expected correct behavior?
Service Account tokens should produce correct data when executing the query.
Relevant logs and/or screenshots
The logs shows that the query executed successfully with a 200 response.