Planner allows changes to older versions of resources, if the intended change does not conflict with newer changes accepted by the Planner service on the same resource.
#PLANNER PRO APP WEB ACCESS PATCH#
PATCH and DELETE requests require the last etag known by the client to be specified with a If-Match header. These etags are returned with property on each resource.
Planner versions all resources using etags. The custom columns in the bucket task board are represented by bucket objects, and their order by orderHint property on the object.Īll the ordering is controlled by the principles described in Planner order hints. Tasks are shown asīoard view with columns for assignees (assigned to task board)īoard view with columns for progress of the task towards completion (progress task board)īoard view with custom columns of tasks (bucket task board): Several types of visualization data are available for tasks, as listed in the following table. VisualizationĪside from task and plan data, the Planner API also provides resources for creating a common visualization of data across clients. Basic objects provide access to common properties of the resources, suitable for list views, while the detail objects provide access to large properties of the resources suitable for drill down views. Planner resources are arranged into basic objects and detail objects. The ID of the user to assign the task is the name of the open property on assignments, and the orderHint property on the assignment must be specified. GET /groups//tasksĮach task can be assigned to a user by adding an assignment in the assignments property on the task object. To get the plans owned by a group, make the following HTTP request. Microsoft 365 groups are the owners of the plans in the Planner API.
You can use the Planner API in Microsoft Graph to create tasks and assign them to users in a group in Microsoft 365.īefore you get started with Planner API, you will want to understand how the main objects relate to each other as well as to Microsoft 365 groups.