> For the complete documentation index, see [llms.txt](https://docs.forgappify.com/field-rules/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.forgappify.com/field-rules/rules/enable-self-assignment-only.md).

# Enable self-assignment only: restrict Assignee to the current user

Restrict the Assignee field in Jira so users can only assign a work item to themselves. Self-assignment only, enforced with no scripting.

Field Rules can restrict the Assignee field so a user can only assign a work item to themselves, not to anyone else. If a user selects any other assignee, the selection is immediately reverted and an error message is shown - a self-assignment-only restriction that standard Jira permissions cannot express, enforced with no code.

***

## How to set it up

1. Open the **UI Modification** for the context you want to control (space, work type, and view). The rule always targets the Assignee field - there is no field selection step.
2. Add an **Enable self-assignment only** rule.
3. *(Optional)* Set a custom **Validation message** shown when a user picks someone else. Without one, a default message is shown.
4. *(Optional)* Edit the **Description** shown on the Assignee field, so the restriction is signalled before the user tries an invalid selection. A new rule starts with a default description; clear it to keep the Assignee's own description. It supports basic wiki markup (bold, links, color); see [Formatting the description](https://docs.forgappify.com/field-rules/rules/use-description.md#formatting-the-description).
5. *(Optional)* Add **preconditions** - field values and/or user identity - to scope enforcement. Leave empty to enforce for everyone in the context.
6. Save. The rule now reverts any assignee other than the current user.

<figure><img src="https://1561395444-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOfQTst0rZQxXAZF84TB5%2Fuploads%2Fgit-blob-1669732ca90e8a86aa20725c5abff7ee20cec14c%2Fenable-self-assignment-rule-except-project-managers.png?alt=media" alt="Configuring an Enable self-assignment only rule with a custom message and description, exempting the Project Managers group"><figcaption><p>Enforcing self-assignment for everyone except the Project Managers group, with a description hint.</p></figcaption></figure>

| Option                 | Description                                                                                                                                                                            |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Validation message** | The error message shown to the user when an invalid assignee is selected. Maximum 255 characters. Without one, a default message is shown.                                             |
| **Description**        | The Assignee field's description while the rule applies, visible below the field. A new rule starts with a default description; leave it empty to keep the Assignee's own description. |
| **Preconditions**      | Optional field and/or user conditions. Leave empty to always enforce the rule.                                                                                                         |

***

## How it works

A configured description is shown as soon as the screen opens. The assignee is checked only when the user changes it, so a work item already assigned to someone else, or a default assignee, is left as it is. If the user picks another person, the Assignee is reverted to the value it had when the screen opened and an error flag appears with the configured message. Selecting yourself, Unassigned or Automatic is always allowed.

The rule does not prevent the Assignee field from being opened or browsed.

***

## Preconditions

Preconditions are optional. Without them, the rule applies to all users in the UIM's configured context.

Use preconditions to restrict enforcement to a subset of users or situations:

* **User conditions** - enforce only for specific users, groups, or roles. For example, apply the rule to everyone except members of the "Project Managers" group.
* **Field conditions** - enforce only when another field matches a value. For example, only restrict self-assignment when the Issue Type is "Task".

***

## Behaviour when reverted

When a user selects an invalid assignee:

1. The Assignee field is immediately set back to the value it had when the screen opened.
2. An error flag appears with the configured validation message.

***

## Examples

**Enforce self-assignment for all users**\
Add the rule with no preconditions. Every user in scope can only assign work items to themselves or leave the field unassigned.

**Exempt project managers**\
Add a user condition set to "Except" and select the "Project Managers" group. The restriction applies to everyone else, while project managers can assign freely.

**Restrict self-assignment to a specific work type**\
Add a field condition: Issue Type is one of "Task". The rule only enforces self-assignment when a Task is being created or edited; other work types are unaffected.

**Hint the restriction upfront**\
Set the description to "You can only assign this work item to yourself." The text appears below the Assignee field before the user interacts with it, reducing confusion.

***

## When to use it

Use Enable self-assignment only for a pull-based workflow, where people should pick up their own work rather than assign it to others:

* **Self-service queues** - a support or task queue where anyone can claim an item, but not hand it to someone else.
* **Scoped to a work type or group** - combine with preconditions so the restriction only applies where it matters, and exempt leads who need to assign broadly.

***

## Doing this without Field Rules

Standard Jira Cloud has no self-assignment-only mode. The "Assign Issues" project permission is all-or-nothing: a user either can assign work items or cannot, and if they can, they can assign to anyone with that permission in the project - Jira's permission scheme controls whether an action is allowed at all, not who the target of that action may be.

A self-assignment-only restriction requires a UI Modifications app like Field Rules or a scripting app.

See [Field Rules vs native Jira](https://docs.forgappify.com/field-rules/jira-administrator/field-rules-vs-native-jira.md) for the full comparison across every rule.

***

## Limitations

* **JSM Request Create is not supported.** The Assignee field is not available via UI Modifications on the JSM portal.
* **The rule does not prevent leaving the field unassigned or choosing Automatic.** It only blocks assigning to another person. If the Assignee field is required, combine this rule with [Make field required](https://docs.forgappify.com/field-rules/rules/make-field-required.md).
* **UI-level enforcement only.** The rule operates on the work item screen and cannot restrict assignments made via the Jira API or other integrations.
* **On Issue View, an invalid assignee can be saved briefly.** It is reverted right away, but both changes appear in the work item history, and refreshing or leaving the page immediately can keep the invalid assignee. For strict enforcement, use a workflow validator or the Assign Issues permission.
* **Does not grant assignment permission.** If a user lacks the Jira "Assign Issues" project permission, they cannot assign the work item to themselves either - the rule does not bypass or supplement Jira's permission model.

***

## Related rules

* [Make field required](https://docs.forgappify.com/field-rules/rules/make-field-required.md) - make the Assignee field mandatory.
* [Lock field](https://docs.forgappify.com/field-rules/rules/lock-field.md) - make the Assignee field read-only instead of self-only.
* [Use description](https://docs.forgappify.com/field-rules/rules/use-description.md) - override a field's hint text based on conditions.
