title:Multiple Assignees API is now official

author_name:nakajima

We're making[Multiple Assignees][blog-post] part of the official GitHub API.

During the preview period you needed to provide the`application/vnd.github.cerberus-preview` preview media type in the`Accept` header to opt-in to the changes. Now that the preview period has ended, you no longer need to specify this custom media type.

If you have any questions or feedback, please[get in touch with us][contact]!

[blog-post]:/changes/2016-5-27-multiple-assignees/

[contact]:https://github.com/contact?form[subject]=Multiple+Assignees+API

-----|------|--------------

`title`|`string` |**Required**. The title of the issue.

`body`|`string` | The contents of the issue.

`assignee`|`string` | Login for the user that this issue should be assigned to._NOTE: Only users with push access can set the assignee for new issues. The assignee is silently dropped otherwise._

`assignee`|`string` | Login for the user that this issue should be assigned to._NOTE: Only users with push access can set the assignee for new issues. The assignee is silently dropped otherwise.**This field is[deprecated](https://developer.github.com/v3/versions/#v3-deprecations).**_

`milestone`|`integer` | The`number` of the milestone to associate this issue with._NOTE: Only users with push access can set the milestone for new issues. The milestone is silently dropped otherwise._

`labels`|`array` of`strings` | Labels to associate with this issue._NOTE: Only users with push access can set labels for new issues. Labels are silently dropped otherwise._

`assignees`|`array` of`strings` | Logins for Users to assign to this issue._NOTE: Only users with push access can set assignees for new issues. Assignees are silently dropped otherwise._

{{#tip}}

<aname="preview-period"></a>

The`assignees` parameter is currently available for developers to preview.

During the preview period, the API may change without advance notice.

Please see the[blog post](/changes/2016-5-27-multiple-assignees) for full details.

To access the API during the preview period, you must provide a custom[media type](/v3/media) in the`Accept` header:

The`assignees` key will only be accepted in issue payloads if this header is passed.

{{/tip}}

<%= json\

:title => "Found a bug",

:body => "I'm having a problem with this.",

:assignee => "octocat",

:assignees =>[get_resource(:user)],

:milestone => 1,

:labels => %w(bug)

%>

<%= headers 201,:Location => get_resource(:full_issue)['url'] %>

<%= json:full_issue %>

{% if page.version == 'dotcom' %}

{{#tip}}

<aname="preview-period"></a>

An additional`assignees` object in the issue payload is currently available for developers to preview. During the preview period, the APIs may change without advance notice.

Please see the[blog post](/changes/2016-5-27-multiple-assignees) for full details.

To access the API you must provide a custom[media type](/v3/media) in the`Accept` header:

The`assignees` key will be an Array of Users who are assigned to the issue.

{{/tip}}

{% endif %}

Issue owners and users with push access can edit an issue.

-----|------|--------------

`title`|`string` | The title of the issue.

`body`|`string` | The contents of the issue.

`assignee`|`string` | Login for the user that this issue should be assigned to.

`assignee`|`string` | Login for the user that this issue should be assigned to.**This field is[deprecated](https://developer.github.com/v3/versions/#v3-deprecations).**

`state`|`string` | State of the issue. Either`open` or`closed`.

`milestone`|`integer` | The`number` of the milestone to associate this issue with or`null` to remove current._NOTE: Only users with push access can set the milestone for issues. The milestone is silently dropped otherwise._

`labels`|`array` of`strings` | Labels to associate with this issue. Pass one or more Labels to_replace_ the set of Labels on this Issue. Send an empty array (`[]`) to clear all Labels from the Issue._NOTE: Only users with push access can set labels for issues. Labels are silently dropped otherwise._

`assignees`|`array` of`strings` | Logins for Users to assign to this issue. Pass one or more user logins to_replace_ the set of assignees on this Issue. .Send an empty array (`[]`) to clear all assignees from the Issue._NOTE: Only users with push access can set assignees for new issues. Assignees are silently dropped otherwise._

{{#tip}}

<aname="preview-period"></a>

The`assignees` parameter is currently available for developers to preview.

During the preview period, the API may change without advance notice.

Please see the[blog post](/changes/2016-5-27-multiple-assignees) for full details.

To access the API during the preview period, you must provide a custom[media type](/v3/media) in the`Accept` header:

The`assignees` key will only be present in issue payloads if this header is passed.

{{/tip}}

<%= json\

:title => "Found a bug",

:body => "I'm having a problem with this.",

:assignee => "octocat",

:assignees =>[get_resource(:user)],

:milestone => 1,

:state => "open",

:labels => %w(bug)

<%= headers 200 %>

<%= json:full_issue %>

{% if page.version == 'dotcom' %}

{{#tip}}

<aname="preview-period"></a>

An additional`assignees` object in the issue payload is currently available for developers to preview. During the preview period, the APIs may change without advance notice.

Please see the[blog post](/changes/2016-5-27-multiple-assignees) for full details.

To access the API you must provide a custom[media type](/v3/media) in the`Accept` header:

The`assignees` key will be an Array of Users who are assigned to the issue.

{{/tip}}

{% endif %}

{% if page.version == 'dotcom' or page.version >= 2.6 %}

{{#tip}}

<aname="preview-period"></a>

This endpoint is currently available for developers to preview.

During the preview period, the API may change without advance notice.

Please see the[blog post](/changes/2016-5-27-multiple-assignees) for full details.

To access the API during the preview period, you must provide a custom[media type](/v3/media) in the`Accept` header:

{{/tip}}

This call adds the users passed in the`assignees` key (as their logins) to the issue.

{{#tip}}

<aname="preview-period"></a>

This endpoint is currently available for developers to preview.

During the preview period, the API may change without advance notice.

Please see the[blog post](/changes/2016-5-27-multiple-assignees) for full details.

To access the API during the preview period, you must provide a custom[media type](/v3/media) in the`Accept` header:

{{/tip}}

This call removes the users passed in the`assignees` key (as their logins) from the issue.

Recommendation: This attribute no longer dictates the permission a team has on its repositories; it only dictates the default permission that the[Add or update team repository](/v3/orgs/teams/#add-or-update-team-repository) API will use for requests where no`permission` attribute is specified. To change the permission level for every repository on a team, use the[List team repositories](/v3/orgs/teams/#list-team-repos) API to list all of the team's repositories, and then use the[Add or update team repository](/v3/orgs/teams/#add-or-update-team-repository) with a`permission` attribute to update each repository's permission separately.

1. Issue attribute: assignee

Recommendation: Use the[`assignees`](https://developer.github.com/v3/issues/#create-an-issue) key instead, since issues can have more than one assignee. Alternatively, you can use the

[assignees](https://developer.github.com/v3/issues/assignees/) endpoints.

<aid="beta">