How do I give permission to devs so that when they create issue they can only assign to themselves?

[Aamil Nakhuda]

Hello,

I am a Jira administrator in my team and I assign tasks(issues) to developers, testers, etc.

I have came to a situation where the developers want to create an issue for themselves and to assign to themselves only.

I want to restrict developers in issue creation, where only they can create an issue and assign to them selves and no one else. How do I achieve this?

Regards

[John Funk]

Hi Aamil - Welcome to the Atlassian Community!

One way to do this might be with the Permission Scheme where the Assignee, Reporter, Administrator Group, and Administrator Project Role are the only ones with Assignable User permissions. Then set a post function on the Create transition to set the Assignee = the Reporter. (Or you could also do that with an automation rule that fires on an Issue Created trigger. 

Another way is with Issue Level Security. You could create a default Security Level where the Assignee, Reporter, Administrators Group and Administrators Project Role are the only ones with access to the issue. But nobody else would see this issue, and that might be a problem for you. 

[Aamil Nakhuda]

The first solution won't work as we require the Reporter to be either the Testers or the Project Mangers.

The second solution will a definitely be a big problem. 

Any ways thank you so much for your solutions :)

[John Funk]

Well, then use those groups instead of the Reporter. 

[Chris Buzon]

permissions in cloud jira don't really work exactly that way. There are 3 relevant permissions (they are per-project, based on the role the user has in that project).

Assignable user - allows each specific user (in each role) to be assigned issues by anyone else.
Assign Issues - allows each specific user with this role to assign issues to others.
Create Issues - allows each specific user to create new issues (the default assignee is configurable, based on components, automation, post-functions, etc).

You can't really limit them to assigning a ticket to themselves easily, but there are ways you can achieve that goal - I do not suggest doing this, btw.
You'd have to remove the ability to assign users to others, then use automation to set the assignee (to the reporter of the issue) when the ticket is created.  They would also need "create issues" permission in this case. 
This is not a desirable thing to do, usually - since it will affect all ticket types, and will limit the ability of others to assign tickets easily.  Someone would have to manage all the tickets on behalf of the team, and that doesn't usually scale very well.

[Chris Buzon]

another way to do this is through the API - but that is a huge technical ask. I'd encourage you to try other solutions:

-Jira automation rule to alert when someone assigns to something other than themselves.  Send that to slack/teams/you directly and correct the behavior on a case by case basis.

-Jira automation rule that runs manually, and automatically assigns the ticket to the person running the rule (you would remove the assign users permission, and the rule would need to use a different 'actor' to run).

[Aamil Nakhuda]

yes this is too technical and inefficient, but yes thank so much for helping around :)