Problem: isq issue list --json returns every field for every issue. AI agents often need only 2-3 fields (e.g., number, title, priority). This wastes tokens/bandwidth and forces consumers to filter client-side.
Goal: Let consumers request only the fields they need.
Success criteria:
isq issue list --json --select number,title,priority returns only requested fields- Works for
isq issue show and other JSON-outputting commands
- Invalid field names produce helpful error
- Omitting
--select returns all fields (backwards compatible)
Context (Rich Hickey's Maybe Not): Optionality is context-dependent. Different consumers need different subsets of the same data. Don't force one-size-fits-all output.
Problem:
isq issue list --jsonreturns every field for every issue. AI agents often need only 2-3 fields (e.g., number, title, priority). This wastes tokens/bandwidth and forces consumers to filter client-side.Goal: Let consumers request only the fields they need.
Success criteria:
isq issue list --json --select number,title,priorityreturns only requested fieldsisq issue showand other JSON-outputting commands--selectreturns all fields (backwards compatible)Context (Rich Hickey's Maybe Not): Optionality is context-dependent. Different consumers need different subsets of the same data. Don't force one-size-fits-all output.