fix(issue): stop collapsing stats on piped output and JSON defaults (#1221)

## Summary

Fixes #1219. `sentry issue list` was sending `collapse=stats` whenever
stdout was piped or `--json` was used. On the Sentry API that flag skips
all seen-stats Snuba queries — not just sparklines — so piped tables
showed `—`/`?`/`0` for SEEN/AGE/EVENTS/USERS and JSON omitted basic
fields by default.

Now stats are only collapsed when `--json --fields` explicitly omits
count/timestamp/stats fields. Human output (including piped/agent usage)
always requests seen-stats data; the TREND column is still hidden on
narrow terminals as a display-only concern.

## Test plan

- [x] `pnpm exec vitest run test/commands/issue/list.test.ts -t
"collapse"`
- [ ] `sentry issue list <org>/<project> -q "is:unresolved" | head` —
SEEN/AGE/EVENTS/USERS populated
- [ ] `sentry issue list <org>/<project> --json` — includes `count`,
`userCount`, `firstSeen`, `lastSeen`, `stats`

Fixes #1219

Made with [Cursor](https://cursor.com)

---------

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: betegon

.lore.md

@@ -26,7 +26,7 @@
 * **check:stale-refs: generic toolchain consistency scanner derived from package.json**: \`script/check-stale-references.ts\`: reads \`packageManager\` from \`package.json\` (e.g., \`pnpm@10.11.0\`), derives stale PMs dynamically, and scans dev-facing docs/scripts for stale \`\<pm> run\`, \`\<pm> remove\`, \`\<pm> add -d\` commands and \`requires \<pm>\`/\`\<pm> installed\` prerequisite prose. Excludes: user-facing install instructions (fenced code blocks with \`install -g\`/\`add -g\`), the check script itself, and \`node\_modules/\`. Added to CI lint job. \*\*Generic\*\*: if project migrates from pnpm to yarn, changing \`packageManager\` in \`package.json\` auto-flags all \`pnpm run\` references in dev docs — no manual pattern updates needed. Trap: script must exclude itself from scanning or its own JSDoc examples trigger false positives.
 
 <!-- lore:019e6a6c-3c39-71fc-a5a1-fb56b9870039 -->
-* **collapse=lifetime in issue list: LIFETIME\_FIELDS, buildListApiOptions, and API gotcha**: \`src/commands/issue/list.ts\` \`LIFETIME\_FIELDS = new Set(\['count','userCount','firstSeen','lastSeen'])\` — fields stripped by \`collapse=lifetime\` on the list endpoint. \`buildListApiOptions(json, fields)\`: \`collapseLifetime\` only true when \`json && fields !== undefined && fields.length > 0 && !fields.some(f => LIFETIME\_FIELDS.has(f))\`. Human output NEVER collapses lifetime. \`buildIssueListCollapse()\` always starts with \`\['filtered','unhandled']\`, conditionally adds \`'lifetime'\` then \`'stats'\`. \`ISSUE\_DETAIL\_COLLAPSE\` safely includes \`'lifetime'\` — detail endpoint preserves top-level fields regardless. \`IssueViewOutputSchema\` in \`src/types/sentry.ts\` extends \`SentryIssueSchema\` with enrichment fields (\`event\`, \`org\`, \`replayIds\`, \`trace\`) added by \`jsonTransformIssueView\`. Wired via \`schema: IssueViewOutputSchema\` on output config in \`view.ts\`. NOTE: \`count\`/\`userCount\`/\`firstSeen\`/\`lastSeen\` always present on \`issue view\` (detail endpoint) — only potentially absent on \`issue list\` when collapse=lifetime is active.
+* **issue list collapse=stats/lifetime API gotcha: SEEN\_STATS\_FIELDS, LIFETIME\_FIELDS, buildListApiOptions**: On the Sentry list endpoint, \`collapse=stats\` skips \`_get_seen_stats()\` entirely — stripping top-level \`count\`, \`userCount\`, \`firstSeen\`, \`lastSeen\` and the sparkline \`stats\` object (not just TREND). \`src/commands/issue/list.ts\`: \`SEEN_STATS_FIELDS = new Set(\[...LIFETIME_FIELDS, 'stats'])\`; \`shouldCollapseForFields(fields, dependentFields)\` shared by stats/lifetime decisions; \`shouldCollapseStats(json, fields)\` never collapses in human mode; JSON only when \`--fields\` omits all seen-stats fields. \`buildListApiOptions(json, fields)\`: \`collapseLifetime = json && shouldCollapseForFields(fields, LIFETIME_FIELDS)\`. \`buildIssueListCollapse()\` always starts with \`\['filtered','unhandled']\`, conditionally adds \`'lifetime'\` then \`'stats'\`. \`willShowTrend()\` is display-only (hides TREND column on narrow/piped stdout). See #1219. NOTE: \`count\`/\`userCount\`/\`firstSeen\`/\`lastSeen\` always present on \`issue view\` (detail endpoint) — only potentially absent on \`issue list\` when collapse is active.
 
 <!-- lore:019cbaa2-e4a2-76c0-8f64-917a97ae20c5 -->
 * **Consola chosen as CLI logger with Sentry createConsolaReporter integration**: Consola is the CLI logger with Sentry \`createConsolaReporter\` integration. Two reporters: FancyReporter (stderr) + Sentry structured logs. Level via \`SENTRY\_LOG\_LEVEL\`. \`buildCommand\` injects hidden \`--log-level\`/\`--verbose\` flags. \`withTag()\` creates independent instances; \`setLogLevel()\` propagates via registry. All user-facing output must use consola, not raw stderr. \`HandlerContext\` intentionally omits stderr. Telemetry opt-out priority: (1) \`SENTRY\_CLI\_NO\_TELEMETRY=1\`, (2) \`DO\_NOT\_TRACK=1\`, (3) \`metadata.defaults.telemetry\`, (4) default on. Shell completions set \`SENTRY\_CLI\_NO\_TELEMETRY=1\` in \`bin.ts\` before imports. Timing queued to \`completion\_telemetry\_queue\` SQLite table; normal runs drain via \`DELETE ... RETURNING\`. \`ENV\_VAR\_REGISTRY\` in \`src/lib/env-registry.ts\` is single source for all honored env vars; \`topLevel: true\` + \`briefDescription\` surfaces in \`--help\`. Add install-script-only vars with \`installOnly: true\`.

src/commands/issue/list.ts

@@ -46,7 +46,6 @@ import {
 import {
   type IssueTableRow,
   shouldAutoCompact,
-  willShowTrend,
   writeIssueTable,
 } from "../../lib/formatters/index.js";
 import {
@@ -189,27 +188,7 @@ type ListApiOptions = {
 };
 
 /**
- * Determine whether stats data should be collapsed (skipped) in the API request.
- *
- * Stats power the TREND sparkline column, which is only shown when:
- * 1. Output is human (not `--json`) — JSON consumers don't render sparklines
- * 2. Terminal is wide enough — narrow terminals and non-TTY hide TREND
- *
- * Collapsing stats avoids expensive Snuba/ClickHouse aggregation queries,
- * saving 200-500ms per API request.
- *
- * @see {@link willShowTrend} for the terminal width threshold logic
- */
-function shouldCollapseStats(json: boolean): boolean {
-  if (json) {
-    return true;
-  }
-  return !willShowTrend();
-}
-
-/**
- * Fields that depend on the `lifetime` API data. When `collapse=lifetime`
- * is sent, the server omits these from the list response. See #969.
+ * Fields stripped by `collapse=lifetime` on the list endpoint. See #969.
  */
 const LIFETIME_FIELDS = new Set([
   "count",
@@ -218,29 +197,55 @@ const LIFETIME_FIELDS = new Set([
   "lastSeen",
 ]);
 
+/**
+ * Fields populated by Snuba seen-stats queries on the list endpoint.
+ *
+ * On the Sentry API, `collapse=stats` skips `_get_seen_stats()` entirely,
+ * stripping top-level count/timestamp fields and the sparkline `stats` object
+ * — not just the TREND column data. See #1219.
+ */
+const SEEN_STATS_FIELDS = new Set([...LIFETIME_FIELDS, "stats"]);
+
+/**
+ * Whether collapse is safe for a `--fields` subset — true when explicit fields
+ * were requested and none depend on the given API data.
+ */
+function shouldCollapseForFields(
+  fields: string[] | undefined,
+  dependentFields: ReadonlySet<string>
+): boolean {
+  return (
+    fields !== undefined &&
+    fields.length > 0 &&
+    !fields.some((f) => dependentFields.has(f))
+  );
+}
+
+/**
+ * Determine whether stats data should be collapsed (skipped) in the API request.
+ *
+ * Collapsing stats saves ~200–500ms per Snuba query but also removes basic issue
+ * metadata. Human output never collapses stats; JSON only opts out via `--fields`.
+ */
+function shouldCollapseStats(json: boolean, fields?: string[]): boolean {
+  return json && shouldCollapseForFields(fields, SEEN_STATS_FIELDS);
+}
+
 /**
  * Build the collapse and groupStatsPeriod options for issue list API calls.
  *
  * When stats are collapsed, groupStatsPeriod is omitted (undefined) since
  * the server won't compute stats anyway. This avoids wasted server-side
  * processing and makes the request intent explicit.
  *
- * Lifetime is only collapsed in JSON mode when explicit `--fields` are
- * provided and none of them are lifetime-dependent (`count`, `userCount`,
- * `firstSeen`, `lastSeen`). Human output always needs these for the
- * EVENTS, USERS, SEEN, and AGE columns.
+ * Stats and lifetime are only collapsed in JSON mode with explicit `--fields`
+ * that omit the corresponding dependent fields. Human output always requests
+ * seen-stats data for the EVENTS, USERS, SEEN, and AGE columns.
  */
 function buildListApiOptions(json: boolean, fields?: string[]): ListApiOptions {
-  const collapseStats = shouldCollapseStats(json);
-  // Collapse lifetime only when in JSON mode with explicit --fields that
-  // don't include any lifetime-dependent field. Human output always needs
-  // these (EVENTS, USERS, SEEN, AGE columns), and JSON without --fields
-  // returns all fields.
+  const collapseStats = shouldCollapseStats(json, fields);
   const collapseLifetime =
-    json &&
-    fields !== undefined &&
-    fields.length > 0 &&
-    !fields.some((f) => LIFETIME_FIELDS.has(f));
+    json && shouldCollapseForFields(fields, LIFETIME_FIELDS);
   return {
     collapse: buildIssueListCollapse({
       shouldCollapseStats: collapseStats,

src/lib/api/issues.ts

@@ -60,24 +60,22 @@ export type IssueCollapseField = NonNullable<
  * Build the `collapse` parameter for issue list API calls.
  *
  * Always collapses `filtered` and `unhandled` — the CLI never consumes
- * these in issue list views. Conditionally collapses `stats` when
- * sparklines won't be rendered (narrow terminal, non-TTY, or JSON),
- * and `lifetime` when the caller confirms the lifetime-dependent
- * top-level fields (`count`, `userCount`, `firstSeen`, `lastSeen`)
- * aren't needed.
+ * these in issue list views. Conditionally collapses `stats` when the caller
+ * confirms seen-stats fields aren't needed, and `lifetime` when the caller
+ * confirms lifetime-dependent fields aren't needed.
+ *
+ * **Important:** `collapse=stats` skips Snuba seen-stats queries entirely,
+ * stripping top-level `count`, `userCount`, `firstSeen`, `lastSeen` and the
+ * sparkline `stats` object — not just the time-series. See #1219.
  *
  * **Important:** Despite being documented as removing only the `lifetime`
  * sub-object, `collapse=lifetime` also strips the top-level `count`,
  * `userCount`, `firstSeen`, and `lastSeen` fields from list responses.
  * Only collapse it when those fields are confirmed unnecessary. See #969.
  *
- * Matches the Sentry web UI's optimization: the initial page load sends
- * `collapse=stats,unhandled` to skip expensive Snuba queries, fetching
- * stats in a follow-up request only when needed.
- *
  * @param options - Context for determining what to collapse
  * @param options.shouldCollapseStats - Whether stats data can be skipped
- *   (true when sparklines won't be shown: narrow terminal, non-TTY, --json)
+ *   (true only when `--json --fields` omits all seen-stats-dependent fields)
  * @param options.shouldCollapseLifetime - Whether lifetime data can be skipped.
  *   Defaults to `false` because most output paths need `count`/`userCount`/
  *   `firstSeen`/`lastSeen`. Only set to `true` when `--json --fields` omits

src/lib/formatters/human.ts

@@ -375,9 +375,9 @@ export const TREND_MIN_TERM_WIDTH = 100;
  * Returns `true` when the terminal is wide enough (≥ {@link TREND_MIN_TERM_WIDTH}).
  * Non-TTY output defaults to 80 columns, which is below the threshold.
  *
- * Used by the issue list command to decide whether to request stats data
- * from the API — when TREND won't be shown, stats can be collapsed to
- * save 200-500ms per request.
+ * Display-only — the issue list command always requests seen-stats data from
+ * the API regardless of this value so SEEN/AGE/EVENTS/USERS stay populated
+ * when output is piped. See #1219.
  */
 export function willShowTrend(): boolean {
   const termWidth = process.stdout.columns || 80;