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; } } }

"Default assignee does not have ASSIGNABLE permission" when Assignee is Automatic

Brad Miller_ks68xa

When users attempt to create an issue and leave the Assignee to "Automatic" it returns the following error:

The default assignee does NOT have ASSIGNABLE permission OR Unassigned issues are turned off.

Unassigned Assignees is turned off, which means it should get assigned to the project leader, which is my user account.

If I change the assignee to my user account, the issue is created.

I've re-indexed the project; changed the assignable user to no effect and changed it back (currently granted to the Project lead, Service Desk Team, and Administrators)

Accepted answers

All comments

Kit Friend_pvmg27

What does it say for permissions around who can be assigned in your project permissions? Worth checking your account is added at whatever role it specifies

Brad Miller_ks68xa

It says that members of "Administrators" and "Service Desk Team" as well as the Project lead can be assigned:

My user account is the Project lead and belong to both roles.

The glitch seems to be when the Assignee is left as "Automatic". What I understand should happen is the Default Assignee should be assigned, which is the Project lead, which is my user account. If I explicitly select my user account as the assignee the issue is created.

To add to the weird, this problem was first noticed when issues were being submitted via the customer portal. Now, issues can be created from the customer portal, but not from the Jira UI.

Piotr Serwa

I had the same problem, where default assigne was the project lead and the project lead account was removed.

Siree

This happens because the Project Settings is set to assign to Project Lead rather than Unassigned and the Project Lead is not an assignable user to that project.

A few options to check and fix this.

Easiest way:

Set the default assignee (Project Settings > Details > Default Assignee > Unassigned.

If that's not the intended behavior,

Check if the user account is still active
- If it is, check to make sure that this person is in the Assignable User in the Permission settings (Project Settings > Permissions)
- If the user account is not active, choose an alternate person

Dhruvin Patel_h4wy89

What was the actual cause of this issue?

I am still trying to figure out the solution here.

Daniel Ebers

Hi @Dhruvin Patel

the explanation of @Siree makes sense and should remedy the problem - did you follow the steps?

Cheers,
Daniel

Dhruvin Patel_h4wy89

Yes the issue is resolved

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

atl-gruland