I am getting the above error in projects that I just created but wasn't able to figure out why until now.
I am admin for our Jira instance and I created the project. I made sure that I have the necessary rights but I cannot use the permissions helper because it requires a task to exist in the project, which there isn't since I just created it.
Any ideas on what to check next?
Hi Vinzenz - Welcome to the Atlassian Community!
In the Permission Scheme, make sure that you have Browse Project and Create Issue permissions.
Typically, the Administrators (or jira-administrators) group is either granted those permissions or the Project Role - Administrators is and that group is in that Project Role.
Thanks @John Funk . That already took me a step further. Apparently by default, the role and group "administrators", which I am in, was not assigned. Only Adminstrator role could create issues.
So I went to the permission scheme and wanted to "grant permission" to myself. However, I am not able to complete the update. When I click on "grant", nothing happens. Have you ever experienced that? I am attaching a picture of what I am seeing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As a Jira Administrator, I have not had an instance where I could not update a Permission Scheme.
Can you get to the People section of the Project Settings? And if so, can you update that?
Also, can you share a screenshot of who currently has Create Issues permission in 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.
Thanks for the insight. It really does seem strange and has never happened to me either.
- I do have access to the people screen and I can set new roles there for myself as well. However, none of the roles there match the default permission for creating issues.
- Please see picture attached.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good questions. I am a bit uncertain about these.
My role in the project is "Administrators". In Jira user management I am in the group "administrators". I am not sure whether Jira discriminates lower and upper case names in this context. Do you know that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are in the Administrators project role, and that role is attached to both the Browse Project and Create Issue permissions, then I see no reason why you can't create an issue.
Is ANYONE able to create one?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok. So I still don't know what happened, but I simply applied a standard persmission scheme (since this is a company managed project) and voilà, it works. So it must really have been an issue with the permissions, even though I don't know what the issue was exactly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vinzenz Bruckert ,
welcome to the Atlassian community!
Are u talking about a company managed or team managed project?
Fabio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So, you need to have Create Issue permission in the related permission scheme.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, I figured that. However, that does not seem to work. Please see the other comment stream where we are talking about this as well.
-> Thanks for your help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.