{"_id":"5b0ef5b77692c200039866d3","project":"55d2023b3c74062300aee506","initVersion":{"_id":"5b041424769904000374c5a3","version":"1.11"},"user":{"_id":"57db49de0678030e008a76f8","username":"","name":"Sophat Sam"},"__v":6,"createdAt":"2018-05-30T19:04:23.616Z","changelog":[{"_id":"5b0ef5b77692c200039866d7","update":"The [Issue Object](doc:the-issue-object) now contains `assignees` and `followers`.","type":"added"},{"_id":"5b0ef5b77692c200039866d6","update":"The [Update Issue in a Project](doc:update-issue-in-a-project) endpoint supports multiple user UIDs for the `assigned_to_uids` parameter.","type":"added"},{"_id":"5b0ef5b77692c200039866d5","update":"The [Issue Object](doc:the-issue-object) `assigned_to` attribute will be deprecated in favor of `assignees`.","type":"improved"},{"_id":"5b0ef5b77692c200039866d4","update":"","type":"added"}],"body":"Hello PlanGrid developers!\n\nWe are releasing support for multiple assignees and followers for the [Issues Object](doc:the-issue-object).\n\nThe `assigned_to` attribute will be deprecated in favor of `assignees.` Although the `assigned_to` attribute will continue to return a single assignee, we recommend using `assignees` attribute which will return an array of all assignees.\n\nThe `followers` attribute is also now available as part of the Issues Object, which will list all users are who \"watching\" the issue.\n\nBoth the `assignees` and `followers` attributes will contain arrays of objects that include `type` (which will be `user`) and `uid` (of the applicable user) attributes. \n\nIn addition to exposing multiple assignees in the new `assignees` attribute, we will also support multiple user UIDs in `assigned_to_uids` when using the [Update Issue in a Project](doc:update-issue-in-a-project) endpoint.\n\nCustomers use issues in many ways, including punchlists, QA/QC lists, and assigning tasks to team members. The release of multiple assignees and \"watchers\" gives customers even more flexibility with issues by being able to delegate an issue to multiple parties and allowing stakeholders to be notified of updates to an issue.","slug":"1110-multiple-assignees-and-watchers-for-issues","title":"1.11.0: Multiple assignees and \"watchers\" for Issues"}

1.11.0: Multiple assignees and "watchers" for Issues


Hello PlanGrid developers! We are releasing support for multiple assignees and followers for the [Issues Object](doc:the-issue-object). The `assigned_to` attribute will be deprecated in favor of `assignees.` Although the `assigned_to` attribute will continue to return a single assignee, we recommend using `assignees` attribute which will return an array of all assignees. The `followers` attribute is also now available as part of the Issues Object, which will list all users are who "watching" the issue. Both the `assignees` and `followers` attributes will contain arrays of objects that include `type` (which will be `user`) and `uid` (of the applicable user) attributes. In addition to exposing multiple assignees in the new `assignees` attribute, we will also support multiple user UIDs in `assigned_to_uids` when using the [Update Issue in a Project](doc:update-issue-in-a-project) endpoint. Customers use issues in many ways, including punchlists, QA/QC lists, and assigning tasks to team members. The release of multiple assignees and "watchers" gives customers even more flexibility with issues by being able to delegate an issue to multiple parties and allowing stakeholders to be notified of updates to an issue.
added
The [Issue Object](doc:the-issue-object) now contains `assignees` and `followers`.
added
The [Update Issue in a Project](doc:update-issue-in-a-project) endpoint supports multiple user UIDs for the `assigned_to_uids` parameter.
improved
The [Issue Object](doc:the-issue-object) `assigned_to` attribute will be deprecated in favor of `assignees`.