Couldnt send request.

Dan Berkh May 6, 2021

Couldnt send request.

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

2 answers

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 6, 2021

This is what it says on the tin. 

(Edit - sorry, I should have said this originally, but got stuck into the answer instead and forgot).

But it's not a well-labelled tin.  The error is short, as they should be, but doesn't really tell you what it actually is, let alone why it's that way or how to fix it!

When you raise a request, there is a Jira issue that needs to be created behind it (A request is a layer in front of an issue for the more simple and public thing the customer sees.)

In this case, you have configured the issue such that it has a default assignee that can't be assigned issues in that project.  The issue needs to have an assignee but the one selected (or the absence of one) means Jira can't set it.  

Check the project configuration for the default assignee, and check the global setting for "unassigned issues are not allowed"

0 votes
Alexander Bondarev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 6, 2021

Hi, @Dan Berkh !

You should check your JSM-project-automation. Assignee should have an Agent-license. 

Also it can be configured by components or project-default assignee, but it is a JSM-project in your case.

Documentarion about JSM automation rules.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events