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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I work closely with our sub-contractor, he's never had issues with this. I've duplicated his error, so i don't believe it is our internet issue but rather a Jira bug. Could someone please look into this or suggest any remedy? Thanks.
Hello @Dexter Chai,
Welcome to Atlassian Community!
I’ve seen some issues related to this error and I was able to replicate it by adding a default assignee that doesn’t have assign permissions. For example, someone was added as the default assignee and then, deleted/inactivated from the site.
Can you please confirm if the error is the same as the one from the screenshot?
If that’s the case, please, go to Project settings > Details and check who is the project lead and default assignee and check it to unassigned or add someone else that has permission.
Please, take your time to test and let us know how it goes.
Kind regards,
Angélica
Hi Angelica, thanks for the prompt reply! I changed it to unassigned and it is now working. Appreciate your assistance.
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.