How to Prevent Users from Assigning Tickets to Others?
Asked by Cansu Genc:

Hello Jira Community,

My team and I are using Jira Work Management, and we need your help to solve an issue we're facing. Currently, each user can assign tickets to anyone when a new issue is created or when working on an existing issue. Our goal is to ensure that each user can only assign tickets to themselves (current user) and prevent them from assigning tickets to others.

Additionally, we don't want a "Done" ticket to be reassigned by anyone else. In other words, once a ticket is completed, it shouldn't be reassigned to another user by anyone other than the original assignee.

We would appreciate your suggestions on how to configure Jira to meet these requirements. What permission settings or workflow adjustments should we make to achieve this?

Thank you in advance for your help!


Answers:
author: Cansu Genc
body: ![image_2024_07_04T13_44_30_504Z (1).png](https://community.atlassian.com/t5/image/serverpage/image-id/333512i575B0265C2A3B310/image-size/large?v=v2&px=999 "image_2024_07_04T13_44_30_504Z (1).png")  

Are we sure we are seeing the same screen?

comments: author: Julian Governale
body: It looks like you are using a company-managed project whereas I was thinking of a team-managed one.

Same properties apply, but you set them by clicking the workflow status and then the properties

You are using a Post function in this case

![2024-07-08_08-26-27.png](https://community.atlassian.com/t5/image/serverpage/image-id/333999i313347D35087DA76/image-size/large?v=v2&px=999 "2024-07-08_08-26-27.png")![2024-07-08_08-27-38.png](https://community.atlassian.com/t5/image/serverpage/image-id/333998iFF78E06D263629AC/image-size/large?v=v2&px=999 "2024-07-08_08-27-38.png")


author: Cansu Genc
body: 1. I added a property key to each status in the Workflow section.
2. I added a transition to the first status.
3. I clicked on the transition and reached the step to add a post function.

* Which option should I select here?

Your response is very valuable to me.![image_2024_07_09T05_36_27_540Z (1).png](https://community.atlassian.com/t5/image/serverpage/image-id/334191i927635049125C2FB/image-size/large?v=v2&px=999 "image_2024_07_09T05_36_27_540Z (1).png")  

To be more specific, for example, a ticket was sent to us by our support team. I want only the current user option to appear in the Assignee section. Do not let other names (other users in the group) appear. This is what we are really trying to reach. No user should be able to assign it to anyone else. But it will not automatically assign a person, everyone in the service desk team will only be able to assign it to themselves.  
![1- 1 community.png](https://community.atlassian.com/t5/image/serverpage/image-id/334310i8B0C5E285A4A76F0/image-size/large?v=v2&px=999 "1- 1 community.png")  

<br />

* I gathered my questions. Could you please review step by step?  
  As I indicated in the image labeled 1.1: ![1- community.png](https://community.atlassian.com/t5/image/serverpage/image-id/334311iC5D8A4B60BC2828C/image-size/large?v=v2&px=999 "1- community.png")  
  Here is our workflow. I click on the pending transition section in the Open step. And I see the pending transition screen (image labeled 2). ![2- community.png](https://community.atlassian.com/t5/image/serverpage/image-id/334312i323BF603FEF75090/image-size/large?v=v2&px=999 "2- community.png")  
  I saw 5 post functions. ![3- community.png](https://community.atlassian.com/t5/image/serverpage/image-id/334313iFD417043B7C32F62/image-size/large?v=v2&px=999 "3- community.png")  
  I will add the "assignee to current user" option, but in what order should they be?

  <br />


author: Cansu Genc
body: Permission scheme is here![image_2024_07_09T05_42_43_720Z.png](https://community.atlassian.com/t5/image/serverpage/image-id/334193i60BE9F2D6AE6650B/image-size/large?v=v2&px=999 "image_2024_07_09T05_42_43_720Z.png")


author: Julian Governale
body: I believe your permissions scheme will be just fine.

Here is a step-by-step process for a company-managed process to limit the ability to assign issues to the current User only if you are a non-administrator role. Administrator roles can assign the issue to anyone. Think of this as an override option.

* In my example, the workflow will only have "Backlog", "Selected for Development", "In Progress", and "Done" status

#### Set the workflow properties to limit the manual assignment of issues to the Administrator role {#toc-hId-347839084}

Access your workflow

1. For the first status (Backlog in my case) click the status name
2. Select the Properties option

![2024-07-09_10-56-22.png](https://community.atlassian.com/t5/image/serverpage/image-id/334342i0C12E01C48034DA9/image-size/large?v=v2&px=999 "2024-07-09_10-56-22.png")

**Set the Properties of the status**

1. Property Key: ` ``jira.permission.assign.projectrole`
2. `Property Value: 10002`

`This will make the assignee field read only to non administrator roles`

Apply this same property to all status

**Back in your workflow, create a self-transition**

1. From Backlog to Backlog
2. Called: Assign to Current User

![2024-07-09_11-05-22.png](https://community.atlassian.com/t5/image/serverpage/image-id/334353iA212988DEADDAA3A/image-dimensions/291x418?v=v2 "2024-07-09_11-05-22.png")

**On the self-transition, add the post function to assign the issue to the current user**

1. Click the self-transition
2. select "Post Functions"
3. Add a Post Function
4. Select the Option "**Assign to Current User**"

The order within the post function shouldn't matter as they happen asynchronously I believe.

Publish the workflow

The self-transition will create the action menu option to allow the current user to assign the issue to themselves only. Do this on all the statuses that you want to allow associates to assign tickets to themselves.

`Keep in mind that administrator role will be able to assing to any assoacites.`

The video shows a developer role account with the ability to only assign to themselves via the action menu

![2024-07-09_11-39-47.gif](https://community.atlassian.com/t5/image/serverpage/image-id/334377iEE7FE26095219FAC/image-size/large?v=v2&px=999 "2024-07-09_11-39-47.gif")

The second video shows my account (Administrator Role) being able to assign to any users in the project

![2024-07-09_11-42-17.gif](https://community.atlassian.com/t5/image/serverpage/image-id/334378i9C5350D192EA336C/image-size/large?v=v2&px=999 "2024-07-09_11-42-17.gif")


author: Cansu Genc
body: Great, I'm glad it worked! Thanks so much. But;

For the final scenario, we want to ensure that once an issue is assigned to a user, that user can no longer assign it to someone else, but can only unassign it.

If the current user can only take a ticket for themselves, they should not be able to transfer it to someone else afterward (we want to prevent possible issue transfers between users to track how many tickets each user handles and ensure they can't share issues among themselves).


author: Cansu Genc
body: This explanation was a bit confusing for me, can you explain it in more detail and step by step?


author: Julian Governale
body: For the first part, its might be a multi-step approach here

1. Edit your workflow and for each status set a property to restrict who can assign an issue

    Key: jira.permission.assign.assignee
    Value: leave blank

1. On the first same status, for example, add a self transition (new to new) - call this transition "Assignment" for example
2. Set a rule to assign the ticket to someone
3. Set the assignee to the current user (the user who triggered the rule)
4. On the same transition add a condition to "Restrict to when a field is a specific value"
   1. Set this value to the assignee field
   2. Make it available only when the assignee is empty (This blocks others from running the self-transition when the ticket is assigned already)

**![assignee-transition.png](https://community.atlassian.com/t5/image/serverpage/image-id/333073iA200F90959CC3132/image-size/large?v=v2&px=999 "assignee-transition.png")**

**The process**

Once a ticket is created, the assignment field is not editable, but users can click on the action menu and select the "Assignment" action to have it assigned to them.

The assignee will now be able to change the assignee because of the above property being set on the status and them being assigned the ticket. This will also remove the action menu option now that the ticket is assigned.

In the remaining status' in your workflow, add the same property to the status (not the transition)

For the second part, add the same workflow property to the done status.

[How to restrict the assignment of issues that are already assigned to someone \| Jira \| Atlassian Documentation](https://confluence.atlassian.com/jirakb/how-to-restrict-the-assignment-of-issues-that-are-already-assigned-to-someone-1168846611.html#:~:text=Add%20a%20workflow%20property%20that%20restricts%20the%20%27Assign,while%20issues%20are%20in%20the%20initial%20workflow%20status.)

[Use workflow properties \| Atlassian Support](https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/)

comments: author: Julian Governale
body: Rereading your requirement, you may want to change the property to be something similar. But base this on your current set up as maybe project lead makes more sese in your case.

    Key: jira.permission.assign.projectrole
    Value: "role ID for Adminitrator"

This will then limit who can assign the tickets via the assignee field to just the administrator role but non admin roles will still use the action menu to assign the ticket to them selves

Then you can do that self-transition at each status so someone can run the action menu assign it to themselves.

You would also eliminate the condition that is in place since you want people to be able to assign a ticket to themselves only at any status, but don't add it to the done status, still use this for the done status

    Key: jira.permission.assign.assignee
    Value: leave blank


author: Cansu Genc
body: How should one proceed in the Add Validator and Add Conditions sections?


author: Cansu Genc
body: ![image_2024_07_06T16_03_25_421Z.png](https://community.atlassian.com/t5/image/serverpage/image-id/333833i9085D394BC305868/image-size/large?v=v2&px=999 "image_2024_07_06T16_03_25_421Z.png")![image_2024_07_06T15_54_30_467Z.png](https://community.atlassian.com/t5/image/serverpage/image-id/333834i037637A5EC342FFB/image-size/large?v=v2&px=999 "image_2024_07_06T15_54_30_467Z.png")![image_2024_07_06T15_49_50_225Z.png](https://community.atlassian.com/t5/image/serverpage/image-id/333835iFECB4B9E0A28BD0F/image-size/large?v=v2&px=999 "image_2024_07_06T15_49_50_225Z.png")


Tags: cloud

jira-service-management

jira-service-management-cloud