PUT /rest/api/2/issue/{issueIdOrKey}/assignee

Assigns an issue to a user. Use this operation when the calling user does not have the Edit Issues permission but has the Assign issue permission for the project that the issue is in.

If name or accountId is set to:

This operation can be accessed anonymously.

Permissions required:

Servers

Path parameters

Name Type Required Description
issueIdOrKey String Yes

The ID or key of the issue to be assigned.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
name String No

This property is no longer available and will be removed from the documentation soon. See the deprecation notice for details.

accountId String No

The account ID of the user, which uniquely identifies the user across all Atlassian products. For example, 5b10ac8d82e05b22cc7d4ef5. Required in requests.

active Boolean No

Whether the user is active.

self String No

The URL of the user.

key String No

This property is no longer available and will be removed from the documentation soon. See the deprecation notice for details.

emailAddress String No

The email address of the user. Depending on the user’s privacy setting, this may be returned as null.

expand String No

Expand options that include additional user details in the response.

displayName String No

The display name of the user. Depending on the user’s privacy setting, this may return an alternative value.

locale String No

The locale of the user. Depending on the user’s privacy setting, this may be returned as null.

accountType String No

The user account type. Can take the following values:

  • atlassian regular Atlassian user account
  • app system account used for Connect applications and OAuth to represent external systems
  • customer Jira Service Desk account representing an external service desk

Possible values:

  • "atlassian"
  • "unknown"
  • "customer"
  • "app"
timeZone String No

The time zone specified in the user's profile. If the user's time zone is not visible to the current user (due to user's profile setting), or if a time zone has not been set, the instance's default time zone will be returned.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.