I am trying to raise a bug but getting error User "xxxxxx" doesn't have the 'Edit Issues' permission

[Anushka_Gupta]

I am trying to raise a bug against jira but getting error User "xxxxxx" doesn't have the 'Edit Issues' permission

[Trudy Claspill · Accepted solution]

Hello @Anushka_Gupta 

Welcome to the Atlassian community.

Are you trying to open a bug in your own Jira instance, or in the Jira instance Atlassian makes visible at https://jira.atlassian.com ?

If the latter, Atlassian doesn't allow the public to create Bugs in their instance. If you think you have identified a bug in Atlassian's product your Jira Administrators can open a support case with Atlassian to investigate the issue. Their support portal is at https://support.atlassian.com/contact/#/

[Anushka_Gupta]

@Trudy Claspill yes I have identified a bug in Atlassian's product. Will contact my Jira Administrators and open a support case. Thanks. 

[Amanda Culver]

This question is listed as CLOUD Hosted, I would seriously consider changing the name of your Jira project as it implies that it's hosted on DC.

---

Your "Jira Software Data Center" project is controlled by permissions

 "Jira Software Data Center" > Project Settings > Permissions

if you are an admin, you'll be able to go to the permissions and look for 

To the right of this will be a list of

• groups
• project role(s)
• etc

that are allowed to edit issues in your "Jira Software Data Center" project

The error message is saying that Edit issues permission is granted to a collection of user groups that doesn't include your user (they're not in any of the groups, or they've not been granted the project role(s) listed.

The solution is to add them to

• the group - requires ORG Admin permission
• project role - requires Project Admin permission

There is an (ugly and ill-advised) solution to add the user to

• the permission scheme - requires System Admin permission

This solution is bad practice as

1. the user will remain in the permission scheme even when they leave the company(!) 
2. The permission scheme may be shared and you'd be allowing this individual user edit to all projects that share this permission scheme.

It's always better to manage permissions with groups, etc.

[Anushka_Gupta]

Thanks @Amanda Culver will look into this.