Fix misleading type-aware pm create --help --type <T> "required" list #441

Activity

1. unbraind

   added

   bugSomething isn't workingSomething isn't working

   agent-experienceImproves the AI agent / MCP / CLI ergonomics and token efficiencyImproves the AI agent / MCP / CLI ergonomics and token efficiency

   on Jul 5, 2026
2. coderabbitai commented on Jul 5, 2026

   

   coderabbitaiBot

   on Jul 5, 2026 – with coderabbitai

   More actions

   🔗 Related PRs

   #51 - Polish CLI ergonomics, delete safety, and templates dedup [closed]

   ---

   📝 Issue Planner

   _{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

   • Create Plan

   ---

   🧪 Issue enrichment is currently in open beta.

   You can configure auto-planning by selecting labels in the issue_enrichment configuration.

   To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

   issue_enrichment:
     auto_enrich:
       enabled: false

   💬 Have feedback or questions? Drop into our discord!
3. unbraind commented on Jul 11, 2026

   

   unbraind

   on Jul 11, 2026

   OwnerAuthor

   More actions

   pm tracker item:

   • pm-qmjx — Fix misleading type-aware pm create --help --type <T> "required" list #441: type-aware create help mislabels applicable flags as required (ignores create-mode)
4. unbraind commented on Jul 12, 2026

   

   unbraind

   on Jul 12, 2026

   OwnerAuthor

   More actions

   Reproduced at runtime in pm 2026.7.11 (not just in --help text). The default create-mode enforces ALL type-applicable fields — including optional metadata links — as required, even when the type's builtin schema defines no required fields.

   Repro:

   $ pm create issue "repro test" --priority 1
   Error: Missing required options
     Missing required options --acceptance-criteria/--ac, --assignee, --author, --body, --comment, --deadline, --dep, --description, --doc, --estimate/--estimated-minutes, --file, --learning, --message, --note, --status, --tags, --test for type "Issue"
   

   But:

   $ pm schema show Issue
   type: Issue
   source: builtin
   folder: issues
   

   → the builtin Issue schema declares no required fields, yet doc/file/test/dep/learning/note/comment (links/metadata normally added after creation) are treated as mandatory. This directly contradicts the issue body's claim that "pm create --title x --type Task --status open (3 flags) succeeds in the default mode" — for issue in default mode it does NOT succeed; the only working path is --create-mode progressive:

   $ pm create issue "..." --priority 1 --tag production --parent pm-futr --create-mode progressive
   → created pm-b8er
   

   So the bug is not limited to the help text: the runtime required-field set equals the full applicable-field set, ignoring (a) the schema's required-field declarations and (b) the active --create-mode. Recommend the runtime enforcement use the same genuinely-mandatory computation described in the proposed fix (default mode → only --title/--type; strict mode → schema-declared required; progressive → minimal), and exclude link/metadata fields (doc/file/test/dep/learning/note/comment) from being mandatory on create.
5. unbraind

   closed this as completedin #957on Aug 10, 2026