Description
When executing m365 planner task add with a description, the returned response always has the property hasDescription: false.
Example response:
{
"planId": "oUHpnKBFekqfGE_PS6GGUZcAFY7b",
"bucketId": "vncYUXCRBke28qMLB-d4xJcACtNz",
"title": "Important task",
"orderHint": "8585269241124027581",
"assigneePriority": "",
"percentComplete": 50,
"startDateTime": "2023-01-20T00:00:00Z",
"createdDateTime": "2023-01-25T21:39:33.0748226Z",
"dueDateTime": "2023-02-15T00:00:00Z",
"hasDescription": false, <------------------------------------
"previewType": "automatic",
"completedDateTime": null,
"completedBy": null,
"referenceCount": 0,
"checklistItemCount": 0,
"activeChecklistItemCount": 0,
"conversationThreadId": null,
"priority": 5,
"id": "D-ys8Ef4kEuwYG4r68Um3pcAAe9M",
"createdBy": {
"user": {
"displayName": null,
"id": "b2091e18-7882-4efe-b7d1-90703f5a5c65"
},
"application": {
"displayName": null,
"id": "31359c7f-bd7e-475c-86db-fdb8c937548e"
}
},
"appliedCategories": {},
"assignments": {},
"description": "Lorem ipsum dolor sit amet, consectetur adipiscing elit.",
"references": {},
"checklist": {}
}Note that we have a description property but also hasDescription: false
Steps to reproduce
Execute m365 planner task add with --description "Lorem ipsum"
Expected results
hasDescription: true
Actual results
hasDescription: false
Diagnostics
No response
CLI for Microsoft 365 version
v6.2.0
nodejs version
v16.18.1
Operating system (environment)
Windows
Shell
PowerShell
cli doctor
No response
Additional Info
This happens because we first create the Planner task, and when that's done, we update the task to set the description. At the end, we return the result we got when we created the task.
We could fix this by setting the hasDescription property to true manually when a description is specified.
Description
When executing
m365 planner task addwith a description, the returned response always has the propertyhasDescription: false.Example response:
{ "planId": "oUHpnKBFekqfGE_PS6GGUZcAFY7b", "bucketId": "vncYUXCRBke28qMLB-d4xJcACtNz", "title": "Important task", "orderHint": "8585269241124027581", "assigneePriority": "", "percentComplete": 50, "startDateTime": "2023-01-20T00:00:00Z", "createdDateTime": "2023-01-25T21:39:33.0748226Z", "dueDateTime": "2023-02-15T00:00:00Z", "hasDescription": false, <------------------------------------ "previewType": "automatic", "completedDateTime": null, "completedBy": null, "referenceCount": 0, "checklistItemCount": 0, "activeChecklistItemCount": 0, "conversationThreadId": null, "priority": 5, "id": "D-ys8Ef4kEuwYG4r68Um3pcAAe9M", "createdBy": { "user": { "displayName": null, "id": "b2091e18-7882-4efe-b7d1-90703f5a5c65" }, "application": { "displayName": null, "id": "31359c7f-bd7e-475c-86db-fdb8c937548e" } }, "appliedCategories": {}, "assignments": {}, "description": "Lorem ipsum dolor sit amet, consectetur adipiscing elit.", "references": {}, "checklist": {} }Note that we have a description property but also
hasDescription: falseSteps to reproduce
Execute
m365 planner task addwith--description "Lorem ipsum"Expected results
hasDescription: true
Actual results
hasDescription: false
Diagnostics
No response
CLI for Microsoft 365 version
v6.2.0
nodejs version
v16.18.1
Operating system (environment)
Windows
Shell
PowerShell
cli doctor
No response
Additional Info
This happens because we first create the Planner task, and when that's done, we update the task to set the description. At the end, we return the result we got when we created the task.
We could fix this by setting the
hasDescriptionproperty totruemanually when a description is specified.