Hi,I a project administrator and i want to grant developpers to create issues.In Project settings\Permissions for "Create Issue", I haveProject Role (atlassian-addons-project-access)Application access (Any logged in user)but developpers cannot create issue.There is an error : "User doesn't have the "Manage projects" permission".I don't want set the "Administer projects" permission to a developper.how can i do?

Community
Products
Jira
Questions
How to grant a developer to create an issue in a project?

How to grant a developer to create an issue in a project?

Hi,

I a project administrator and i want to grant developpers to create issues.

In Project settings\Permissions for "Create Issue", I have

Project Role (atlassian-addons-project-access)
Application access (Any logged in user)

but developpers cannot create issue.

There is an error : "User doesn't have the "Manage projects" permission".

I don't want set the "Administer projects" permission to a developper.

how can i do?

2 answers

1 accepted

1 vote

Answer accepted

Hello @Laurent Houdusse

Where is the error message being displayed? What actions are being executed and who is executing them?

What steps are the developers going through to try to create issues?

Is the project a Company Managed project or a Team Managed project? It will say which it is in the bottom left in the navigation pane.

Is it a Service project, a Software project, or a Business/Work Management project?

Are the users able to see issues in the project? Are they able to take any other actions on the issues, like editing them or adding comments?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

The error is displayed in the "Create issue" popup when a user logged with a developper account on the project "BORA Connect" want to create an issue

The project is a company managed software project

Developpers can see issues in the project and can change issue status and adding comments

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Could you try using the Permissions Helper to try to zero in on why Jira has determined that the Manage Projects permission is needed?

https://support.atlassian.com/jira-cloud-administration/docs/use-the-jira-admin-helper/

The permission should not be needed for simply creating issues. Typically Browse Projects and Create Issues is sufficient.

Can you tell us what fields are available in the Create Issue screen, and which fields the developer is setting?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

The Permissions Helper says that the devlopper has the Create Issue permission and the Browse Projects permission. I don't find a Manage projects permission in the list but perhaps i mistranslated and it's "Administer Projects"

The developper set the description, the sprint and assign to him

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Can you show us the full output of the Permissions Helper?

Can you tell us what fields are available in the Create Issue screen, and which fields the developer is setting?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Here the output

Fields available are

Project
Issue type
Summary
Reporter
Description
Priority
Linked issue
Assignee
Sprint

And developper set

Project
Issue type
Summary
Reporter
Description
Priority
Assignee
Sprint

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

For an already existing issue is the user able to edit all the fields that they are trying to set when creating an issue?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi @Trudy Claspill

Sorry for the delay of this answer.

The user can edit all fields. After tests, I find that user can create issue of another type.

The issue type that cannot be created has the same sreen scheme, the same field configuration but has a different workflow.

What could create the error at the workflow level?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello @Laurent Houdusse

There may be a Validator on the Create transition in the workflow for that issue type. You will need to Edit the workflow to investigate this.

You might want to make a copy of that workflow to open in Edit mode, rather than opening the original workflow in Edit mode.

Once you have the workflow open in Edit mode, find the Create transition. It will be between a circle and the initial status that your newly created issues use.

Screen Shot 2023-01-18 at 8.43.26 AM.png

Click on that arrow/transition and you'll see a pop up display.

Screen Shot 2023-01-18 at 8.43.43 AM.png

Click on Validators in that pop up and you'll see another screen display something like this.

Screen Shot 2023-01-18 at 8.44.01 AM.png

It is here that another Jira Administrator may have added another Validator to limit the creation of this issue type to only people who have a certain permission or belong to a certain role. By default, the Validators for a Create transition will look like what I've shown, but it is possible that it was modified in your environment in this specific workflow.