Commit 3bcd5de
authored
## Problem
When resolving an issue by short ID (e.g., `sentry issue view CLI-BM`)
fails with 404, the error shows:
```
ApiError: Failed to resolve short ID: 404 Not Found
```
This doesn't tell the user what short ID was searched, which
organization was searched, or what to do next. Affects **27 users**
([CLI-A1](https://sentry.sentry.io/issues/7297901204/)).
## Fix
Enhanced the 404 error in `getIssueByShortId` to include context and
suggestions:
```
Short ID 'CLI-BM' not found in organization 'sentry'.
The issue may have been deleted or merged
Verify the short ID and org: sentry issue view sentry/CLI-BM
List issues in this org: sentry issue list sentry/
```
## Design Decisions
- **Keeps ApiError type**: The enhanced error still has `status=404`, so
`tryGetIssueByShortId` (used for parallel fan-out across orgs) continues
to work unchanged — it catches `ApiError` by status code
- **Inline detail**: Suggestions are formatted as the ApiError `detail`
field, which `ApiError.format()` renders on indented lines below the
main message
- **Context-aware**: Includes the actual short ID and org slug so users
can verify both
1 parent 0714d27 commit 3bcd5de
1 file changed
+21
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
237 | 237 | | |
238 | 238 | | |
239 | 239 | | |
240 | | - | |
| 240 | + | |
| 241 | + | |
| 242 | + | |
| 243 | + | |
| 244 | + | |
| 245 | + | |
| 246 | + | |
| 247 | + | |
| 248 | + | |
| 249 | + | |
| 250 | + | |
| 251 | + | |
| 252 | + | |
| 253 | + | |
| 254 | + | |
| 255 | + | |
| 256 | + | |
| 257 | + | |
| 258 | + | |
| 259 | + | |
| 260 | + | |
241 | 261 | | |
242 | 262 | | |
243 | 263 | | |
| |||
0 commit comments