You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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)
What was the actual cause of this issue?
I am still trying to figure out the solution here.
the explanation of @Siree makes sense and should remedy the problem - did you follow the steps?
Cheers,
Daniel
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had the same problem, where default assigne was the project lead and the project lead account was removed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This worked. Thank Siree
Set the default assignee (Project Settings > Details > Default Assignee > Unassigned
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.