Problem
The lark-workflow-standup-report workflow and the task +get-my-tasks reference still encourage a standup pattern that can include completed tasks by accident.
In a standup / daily-summary scenario, the recommended command is:
lark-cli task +get-my-tasks --due-end "2026-05-20T23:59:59+08:00"
But without --complete=false, this returns both completed and incomplete tasks.
Issue #164 already covers the base command behavior. This new issue is about the workflow/reference layer still assuming "my tasks before due date" is suitable for pending-task summaries without explicitly filtering incomplete tasks.
Why this matters
This causes daily standup summaries to surface completed tasks as if they were still pending.
Real example from my environment:
lark-cli task +get-my-tasks --due-end '2026-05-20T23:59:59+08:00' returned 26 tasks
- after checking task details, multiple returned tasks had
status=done
lark-cli task +get-my-tasks --complete=false --due-end '2026-05-20T23:59:59+08:00' reduced the result to 4 actual pending tasks
Several tasks included by the default standup-style query were already completed, for example:
老百姓5月7日复盘会议 - 报告与工单数据确认
确定参会人员和议程
准备会议PPT和材料
亚玛芬Wilson项目启动会材料
Each of the above returned status=done in task.tasks.get.
Current mismatch
- The standup workflow says or implies this is a pending-task summary flow.
- The
task +get-my-tasks reference includes examples that are easy to copy into standup summaries.
- In practice, a standup summary needs
--complete=false explicitly.
Suggested fix
Update workflow/docs/examples to use:
lark-cli task +get-my-tasks --complete=false --due-end "<end-of-day>"
Specifically:
- update
lark-workflow-standup-report
- update any
task +get-my-tasks summary examples that imply pending-only behavior
- optionally add a note in the standup workflow explaining that omitting
--complete can include completed tasks
Environment
@larksuite/cli version 1.0.34
- macOS
- user identity
Problem
The
lark-workflow-standup-reportworkflow and thetask +get-my-tasksreference still encourage a standup pattern that can include completed tasks by accident.In a standup / daily-summary scenario, the recommended command is:
lark-cli task +get-my-tasks --due-end "2026-05-20T23:59:59+08:00"But without
--complete=false, this returns both completed and incomplete tasks.Issue #164 already covers the base command behavior. This new issue is about the workflow/reference layer still assuming "my tasks before due date" is suitable for pending-task summaries without explicitly filtering incomplete tasks.
Why this matters
This causes daily standup summaries to surface completed tasks as if they were still pending.
Real example from my environment:
lark-cli task +get-my-tasks --due-end '2026-05-20T23:59:59+08:00'returned 26 tasksstatus=donelark-cli task +get-my-tasks --complete=false --due-end '2026-05-20T23:59:59+08:00'reduced the result to 4 actual pending tasksSeveral tasks included by the default standup-style query were already completed, for example:
老百姓5月7日复盘会议 - 报告与工单数据确认确定参会人员和议程准备会议PPT和材料亚玛芬Wilson项目启动会材料Each of the above returned
status=doneintask.tasks.get.Current mismatch
task +get-my-tasksreference includes examples that are easy to copy into standup summaries.--complete=falseexplicitly.Suggested fix
Update workflow/docs/examples to use:
lark-cli task +get-my-tasks --complete=false --due-end "<end-of-day>"Specifically:
lark-workflow-standup-reporttask +get-my-taskssummary examples that imply pending-only behavior--completecan include completed tasksEnvironment
@larksuite/cliversion1.0.34