Hello @Aya Bouznari
Welcome to the Atlassian community.
What steps specifically were you executing before receiving that message? Were you trying to create the issue through the UI or through an API call?
If it's not in the permission scheme then check the workflows create transition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can check your Jira access role in project and the Permission scheme.
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 created 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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Juan Jimenez -- Welcome to the Atlassian Community!
This is a very old thread, and so please create a new question using the "Ask a question" button at the top of the page. This will ensure the maximum number of people see your question to offer suggestions. Thanks!
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
look at the permission scheme assigned to the project and see what roles can create issues
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.