[sentry-junior]

Part of #1564. Dashboard commands parsed their positionals by hand inside func, and issue commands used their own grammar (#1729). This moves both onto the shared ID grammar (grammar/id-arguments.pegjs, #1714), parsed before func runs. Event view's issue checks (#1733, #1738) use the new issue kind too.

Shared grammar: kinds with names. IdKind.names adds one idea to id-arguments.pegjs: a kind may name an item without its ID, and anything that is not, and may not be, an ID is a name. Kinds without names keep their grammar paths exactly as before. Kinds with names keep each line whole (no splitting at spaces), so Top 10 stays one title and never becomes title Top + ID 10.

• ID_KINDS.dashboard: a numeric ID or a title, which may hold spaces and slashes (Latency/p95). <org>/[<project>/]<digits> reads as a path only when slugs come before the digits, so Errors.v2/123 and /123 are titles. After a target, the title takes the rest of the arguments (my-org/ My Dashboard). A bare first word names an org (orgScoped).
• ID_KINDS.issue: an identifier (numeric ID, short ID, selector, issue URL) is one whole token (wholeIds). src/lib/issue-identifier.ts takes it apart with the ref(cli): Parse issue arguments with their own grammar, before the command runs #1729 grammar, which is unchanged. Text with spaces is a name, meaning a search.
• dashboard-arguments.pegjs is gone. dashboard list keeps its thin parseDashboardListArgs, because a bare word there is a title filter (see ref(cli): Parse list command targets in their positional #1711).

Bare first word: org or title? For dashboard view My Dashboard, the parser makes no decision. It returns the structural reading (org My, title Dashboard) and the whole input as one title (nameWithTarget, surfaced as orgOrTitle). resolveDashboardInput decides after auth:

• First it checks whether My is an org: the cached org list and region cache, then GET /organizations/My/ only on a cache miss.
• If the org exists, the title lookup in that org is final, even when it misses.
• On a 404 or 403 it warns No org 'My'; treating "My Dashboard" as the dashboard title. Use my-org/ to name an org. and looks up "My Dashboard" in the auto-detected org.
• If that misses too, one error names both readings (no org My to find Dashboard in, and no My Dashboard in <detected-org>) and hints at <org>/ Dashboard and at quoting.
• A 5xx or network error from the org check propagates, with no fallback.
• It never falls back for my-org/ … (explicit org), a numeric ref, or a URL.

Issue search text. issue view "login timeout" resolves through GET /organizations/{org}/issues/?query=… in the detected org. One hit is the issue. Zero or several hits raise a ResolutionError that lists up to 5 candidates as runnable commands and points at sentry issue list <org>/ --query '…'. I checked the endpoint against getsentry/sentry (organization_group_index.py, group_index/index.py): query takes free text, an exact event ID or short ID gets a fast lookup, and an explicit query replaces the default is:unresolved.

Search hints. Text where a trace, span, log, or replay ID belongs (trace view login) now fails with Not a trace ID: "login". To search, try `sentry trace list --query 'login'`.. The hint comes from validate(), so commands that recover malformed IDs (trace view, span view, log view) recover first and use the hint only as their final error. Event IDs get no hint, because event list lists one issue's events.

event view. ID_KINDS.issue.distinctForm (uppercase short ID or numeric) replaces looksLikeIssueShortId + isAllDigits and keeps #1738's order: <org>/<short-id>, then <short-id>/<event-id> (even an all-digit event ID), then <org>/<numeric-id>. I added a regression test for the all-digit event ID and one for that order.

Behavior changes:

• dashboard view my-org My Dashboard (unquoted title) looks up "My Dashboard". Before, it used My and dropped Dashboard. The same goes for my-org/ My Dashboard and https://acme.sentry.io/ My Dashboard.
• dashboard view My Dashboard: when there is no org My (404/403), it falls back to the title "My Dashboard" in the detected org, with the warning above. If neither reading finds a dashboard, one error names both. Dashboard commands with one dashboard ref get this (view, restore, revisions, widget edit/delete, and widget add after it splits off its widget title).
• A numeric ref first is the dashboard, as with every ID kind: dashboard view 42 X, my-org/42 X. Before, the first of two arguments was always the target. After a target, a numeric ID keeps the rest as extra (my-org 123 extra → ID 123, ignored extra) instead of joining them into a title. Arguments after the ID go through the shared rules: extra, reversed (42 my-org/), or the shared "reference different projects" error when they name another target.
• A lone non-Sentry URL is no longer taken as a dashboard title.
• issue view "login timeout" (text with spaces) searches instead of failing as a malformed identifier. Control characters and URLs are still rejected.
• Trace/span/log/replay IDs that are plain text get a search hint instead of "Invalid trace ID".
• Parse errors (no dashboard, an org URL without a dashboard, a dashboard URL passed to list, an invalid target slug) fail before the auth guard, as in the earlier commits on this branch. They print Failed to parse "…" for <placeholder>: … and exit 252.
• widget add/edit/delete: an argument error comes before flag errors like "Specify --index or --title". widget add's positional completes cached dashboards. parseDashboardTarget had no callers left and is removed.

Lint ratchet (#1739): the dashboard entries are off both allow-lists, since these commands now parse before func. The issue entries (issue/utils.ts, issue/merge.ts, which need an array issue positional) stay.

Syncing: this branch merges main (no rebase). 54ebfa2 and 7f52f19 merge #1729, #1732–#1734, #1736, #1738 and #1739.

Verification:

• tsc, pnpm run lint (oxlint, format, ast-grep) and scripts/cli-lint-rules.test.mjs (70/70) pass.
• vitest on test/lib, test/grammar and the dashboard, issue, event, trace, span, log, replay and feedback command tests: 10,158 passed. The 6 failures are the sandbox-only permission tests (completions EACCES/EPERM, code-scanner, file-changes, telemetry readonly, upgrade lock), which also fail on main. The full CLI suite shows the same 6, plus e2e/eval files that need a build or credentials.
• New tests:
  • The bare-org fallback: the org from cache and from the API (no fallback), org missing then fallback hit with the warning, a 403, org missing then fallback miss with the combined error, a 5xx (propagates, no fallback), my-org/ My Dashboard, and a numeric ref.
  • Issue search with 0, 1 and several hits.
  • Search hints, including validate: false deferral.
  • fix(cli): Keep all-digit event IDs after <short-id>/ as events #1738's event view order.
• Differential runs against this PR's previous parsers:
  • Issue arguments: 8,575 cases. 1,388 former errors are now searches (text with spaces), with 0 other differences.
  • Dashboard view: 32,552 cases over 0–3 arguments. Every difference is in one of the categories above: a numeric ID first (2,600), arguments after a dashboard URL that name another target (688), a numeric ID after a target with more words (475), and a lone non-Sentry URL (1).

via BYK.

--

View Junior Session in Sentry

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Oct 29, 2026 9:40pm UTC

[BYK]

Question: can we not extend the existing <id> parsers to <id-or-title> and maybe use it for search? I can see this then being used for issues too. Not sure if replays have titles but we may use this for traces, spans, logs etc. to matche on something?

Too stretched?

[BYK]

dashboard view my-org My Dashboard (unquoted title) still uses My, but now warns that Dashboard was ignored instead of dropping it silently.

Can we not make this work somehow?

[sentry-junior]

Can we not extend the existing <id> parsers to <id-or-title> and maybe use it for search? … Too stretched?

Half-stretched, I think. It works for kinds that have a name people actually type, and stops working where there isn't one.

• Dashboards and issues: yes. The grammar stays structural. An IdKind declares that it accepts names (say name: { greedy: true }), and a non-ID ref becomes { name } instead of a target or an error. Each kind resolves the name after auth: a title match for dashboards, a search for issues (one hit → view it, several → list them and ask). The thing that kept dashboards out of id-arguments.pegjs (Top 10 read as title + ID 10, titles with slashes) goes away once name kinds consume the rest of the arguments greedily, instead of splitting an ID off the end.
• Traces/spans/logs/replays: I'd say no. They have no title, so "match on something" really means a search, which list --query already does. If view searched, it would run an unbounded query and pick a result arbitrarily. What I'd do there instead is: when the input isn't an ID, error with a hint like try `sentry trace list --query "…"` .

I'd keep that out of this PR, which is a behavior-preserving move, and do it as a follow-up: add IdKind.name, then fold the dashboard grammar into id-arguments.pegjs if it absorbs titles cleanly. Issue search would be the first new user of it. Want me to open that follow-up after this lands?

dashboard view my-org My Dashboard … Can we not make this work somehow?

Yes, mostly. Two parts:

1. <target> <title words…> → join them. dashboard list already does this for its filter, so view/restore/revisions do the same: my-org My Dashboard → org my-org, title My Dashboard. The only exception is when the ref is all digits: my-org 123 extra still reads 123 as the ID and warns about extra. widget add already splits off its trailing widget title first, so it's unaffected. I'm making this change in this PR.
2. dashboard view My Dashboard (no org) is ambiguous. Today the first bare word is an org (My/). The grammar can't tell my-org Dashboard from My Dashboard; only resolution can. One option: if that org doesn't resolve (not in the cached or known orgs), fall back to the whole thing as a title in the auto-detected org, plus a warning. That's a resolution fallback, not grammar, so it needs your call: do it here, or leave it as "quote it" with a better error hint?