feat(jira): add description support for subtasks created via AddChecklist#472
Merged
zbigniewsobiecki merged 1 commit intodevfrom Feb 22, 2026
Merged
Conversation
…Checklist
The planning agent writes detailed step descriptions (files to modify, specific
changes, testing strategy) in the card body, but this context was lost when
creating bare JIRA subtasks with only a summary. This threads an optional
description through the AddChecklist gadget → PMProvider.addChecklistItem() →
JIRA adapter, where it is converted to ADF and set on the subtask. Trello
checklist items don't support descriptions, so the Trello adapter ignores the
field. The schema change is backward-compatible: items accept string | {name,
description?}.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
descriptionfield through theAddChecklistgadget →PMProvider.addChecklistItem()→ JIRA adapter, so planning agent step details (files to modify, specific changes, testing notes) are set directly on JIRA subtasksitemsschema is backward-compatible: acceptsstring | { name: string; description?: string }, so existing string items continue to workFiles changed
src/gadgets/pm/AddChecklist.tsstring | {name, description?}, updated examplesrc/gadgets/pm/core/addChecklist.tsChecklistItemInputtype, normalize items, pass descriptionsrc/pm/types.tsdescriptionparam onaddChecklistItemsrc/pm/jira/adapter.tscreateIssuesrc/pm/trello/adapter.ts_descriptionsrc/agents/prompts/templates/planning.etatests/unit/gadgets/pm/core/addChecklist.test.tstests/unit/pm/jira/adapter.test.tsTest plan
npm run typecheck— cleannpm run lint— clean (0 errors, only pre-existing complexity warnings in router)npm test— 2506/2506 tests pass🤖 Generated with Claude Code