I’m building a Forge Custom UI app using jira:issueContext, and I’m making a call from the backend like this:
const res = await api.asUser().requestJira(
route`/rest/api/3/issue/${issueIdOrKey}`,
{
headers: { Accept: 'application/json' },
}
);
The issue definitely exists (visible in the Jira UI)
the call returns:
"Issue does not exist or you do not have permission to see it."
What else could cause asUser() to fail with a permission error despite:
- Having the correct scopes
- Being in a valid
jira:issueContext - Passing the correct issue key
Is there a known restriction with Forge apps and issue security levels or project permissions that could block asUser() calls like this?