It is interesting I get this error because I have provided admin access to the project for the user who is trying to connect. My goal is to create a issue under the project via REST API. I checked and user has access to REST API.
In GUI User is able to create Issue but not via REST.
Any suggestions appreciated.
Welcome to the Atlassian Community!
Admin means admin. It does not mean "do everything". You will need to grant them "create issue" permission as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The account you are using for the REST call needs to be granted "create issue" permission in the project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am having exactly the same problem as described above. I have create a Personal Access Token for the very account I am able to create issue types in JIRA through the browser.
This simple command should work:
curl -v -D- -H "Authorization: <pat removed for obvious reasons>" \
-H "Content-Type: application/json" \
--request POST \
--data '{"fields": {"project": { "key": "CIP"},"summary": "curl","description": "curl script","issuetype" : {"name": "Task"}}}' https://<company_name>.atlassian.net/rest/api/3/issue
But it does not with the error:
{"errorMessages":["You do not have permission to create issues in this project."],"errors":{}}
Some AI LLM tool suggested this:
Verify PAT Permissions:
Go to your Atlassian account settings
Navigate to Security > Personal access tokens
Check that your token has the necessary permissions (read:jira-work, write:jira-work)
Consider creating a new token with explicit permissions for issue creation
But I do not see those options on my JIRA installation. I can only create tokens with an expiry date. Nothing else.
This is the JIRA I am using:
Build Number: 100283
Build Date: 2025-04-10T17:15:24.000+0200
Deployment Type: Cloud
If you still think we are doing something wrong, can you suggest some different way of debugging this that is different than what I have tried already?
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.