nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

User can't assign ticket since they're not Assignee but is a Developer

Edgar Oregel_1g2cuw

I am a Jira server administrator, and users have reported that they cannot assign tickets even though they have Developer permissions to the Jira project. The Developer project Role has been added to the "Assing Issues" permission scheme. When i use the Jira Admin Permission helper tool, it has a passed case and a failed case.

Pass: User is part of the Developer role

Failed: User is not the Assignee

Shouldn't they be able to assign the ticket since they meet one of the 2 required permissions? Even I as a Jira Admin couldn't assign the ticket until i removed the "Current Assignee" from the "Assign Issues" permission in the permission scheme.

The reason for having Developers and Current Assignee was because we want only Developers to be able to assign any ticket but also give the Assignee the ability to re-assign a ticket they were accidentally assigned to someone else. The reason for this is because we have people in the "Users" role who only have read-only access to everything other than the tickets that they're assigned to, and they should be able to re-assign the ticket to someone else if they were assigned a ticket by accident or someone assigned it to the incorrect person.,

Accepted answers

Ste Wright

Hi @Edgar Oregel

It's actually possible to do this.

I recreated your scenario - this is the permission set I created:

Edit Permissions: Current Assignee
Assign Issues: Current Assignee, Developers
Assignable User: All Logged-in Users

^ In this example, the Developers role does not have "edit" permissions. However, this does limit the ways in which a Developer can assign an issue - for example:

Edit: Not available
Inline Editing: Failed
Assign Issues button: Passed
Keyboard Shortcut 'a': Passed

^ It's based on how you assign the issue - you can't inline edit (even though it's available) as it's classed as an 'edit' - however, the "Assign Issues" button and the keyboard shortcut 'a' only allow you to assign issues, which meets the criteria of the permission scheme.

This is how you can utilise the permission scheme you need.

Ste

All comments

Parvaneh Zand

Hi @Edgar Oregel ,

1. For your first question, users should have all the required permissions not just some of them.

2. If you don't have edit issue pemission, you can't assign issue to someone else. So "users" with just assign issue permission, can only see "Assign to me" option -> (on issues that are not assigned to them), they can't change the assignee to other users.

Grant edit issue permission to Developers, and remove Current Assignee from Assign issue permission. so developers can assign issues.

Ste Wright

Hi @Edgar Oregel

It's actually possible to do this.

I recreated your scenario - this is the permission set I created:

Edit Permissions: Current Assignee
Assign Issues: Current Assignee, Developers
Assignable User: All Logged-in Users

^ In this example, the Developers role does not have "edit" permissions. However, this does limit the ways in which a Developer can assign an issue - for example:

Edit: Not available
Inline Editing: Failed
Assign Issues button: Passed
Keyboard Shortcut 'a': Passed

This is how you can utilise the permission scheme you need.

Ste

Susheela Kushwaha

I had the same situation but the with following correct permission setup:

Assign issues: any logged in user

Edit issues: any logged in user

but still can't edit the assignee field even as an admin.

Solution: Turns out the 'Assignee' fields has to be present on the view/edit screen for anyone to be able to edit the assignee. Hope this helps.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

permission

assign