Granular API Token: GET /project returns empty list [], but Classic Token works perfectly [N8N]

[mateulusz]

Hi, I am trying to use the new Granular API Tokens (API key with scopes) for an N8N integration, but I am facing a visibility issue.

The Scenario:

Endpoint: GET /rest/api/3/project (or /search)
User: Site Admin (has full access).
Goal: List all projects in the instance (including JSM projects).

The Problem:
When I use a Classic API Token (Basic Auth: Email + Token), the endpoint returns 148 projects.
When I use a Granular API Token (Bearer Auth), the endpoint returns an empty array [] (or 404 when querying a specific key like /project/KEY).

What I have tried:
I created a token with 50+ scopes, including every possible combination of:
read:project:jira
read:user:jira (and read:account)
read:application-role:jira
read:permission:jira
read:instance-configuration:jira
read:servicedesk-request:jira-service-management (since we have JSM projects)

Debugging results:
I checked /rest/api/3/mypermissions?permissions=BROWSE_PROJECTS using the Granular Token, and it returns havePermission: true.
The token works for creating issues (POST /issue), so authentication is successful.

Question:
Why does the Granular Token return an empty project list despite having read:project:jira and BROWSE_PROJECTS permission? Is there a hidden system scope required to “see” the projects list that Classic Tokens have by default?

Thanks for any help!