Mike O
When creating a task with subtasks through the Sunsama connector, I want to supply each subtask's planned time in the same operation.
On September 19, 2026, a ChatGPT connector test reported requesting a 17-minute parent and a 3-minute subtask. The returned subtask was 0 minutes; a later read through the official Sunsama connector in Codex still shows parent 17, subtask 0.
The current
create_task
schema exposes only
title
and
integration
for each subtask. In contrast,
add_subtasks_to_task
accepts a subtask
timeEstimate
, and
edit_task_time_estimate
accepts a
subtaskId
.
Please add
timeEstimate
to subtasks in
create_task
, or explicitly document the required second operation. If an unsupported estimate is supplied, please return a clear warning or error rather than leaving the caller believing it was applied.
To inspect the gap: compare the subtask fields in those two creation tools, create a disposable parent with a subtask, and read back the subtask's planned time. Expected: an explicitly supported requested estimate persists, with the parent's total following the documented subtask aggregation rules.
The original outgoing payload is not available in this review, so this is not yet a confirmed server-side write bug or a failure of
edit_task_time_estimate
. The 3-to-0 behavior is the reported creation-test symptom; the schema inconsistency is independently verified.