Required API Permissions for Jira Service Account

[khronosd]

Describe the problem/error/question

I’m currently working on workflows that involve Jira. During testing, I followed the instructions to use an API token from my account with a full scope. I noticed that Atlassian now offers service accounts along with API access, so I figured I’d swap to that. Unlike the user accounts, you can’t create an API token with a full scope, so you have to be granular in what you choose. I’ve tried a few combinations with no success. This is the most permissive that I gave it so far but still no luck.

What is the error message (if any)?

Information on your n8n setup

• n8n version: [email protected]
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
• Operating system:

[mkitplug]

It doesn’t work for me either.
I’ve tried everything, but I don’t think it’s supported.

[Jakub_Sochan]

The main issue is with how API is called. Jira nodes are made only for authenticating with user email and API token, because (I suspect) they are calling http://your-domain.atlassian.net/rest/api/3/{endpoint}, while with service account you need to call https://api.atlassian.com/ex/jira/{cloudId}/rest/api/3/{endpoint}.

That being said, I managed to set up HTTP node with service account authentication - both API token and oAuth.

Note: I gave token/oAuth all CLASSIC permissions in order not to faff with granularity, and that is pretty much the full scope. What threw me off was you also have to add the service account with required roles to the projects it needs to be able to access/manage