Add issue assign, issue comment, and issue activity commands
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start with the CLI parity inventory and task list linked from the issue, then inspect existing issue and event CLI commands and the relevant @sentry/api operations. Implement the listed issue commands and check whether breadcrumb and user report coverage belongs in existing commands. Done means unit tests pass, parity rows are ticked, and each command has a permission class and exposure if #1880 has landed.
Written by the indexing model from the issue text.
Description
Part of #1357 and #1382 (CLI parity with the MCP). Plan: cli-first-mcp task 2.3 (parity table, tasks).
Under the CLI-first plan the MCP runs CLI commands instead of its own catalog tools, so every catalog tool needs a command before the catalog can go. New commands call the API through @sentry/api operations. They don't wait for the client move (#1875).
Gaps
| MCP tool | Command |
|---|---|
update_issue (assignment) |
issue assign |
add_issue_note |
issue comment |
get_issue_activity |
issue activity |
get_issue_breadcrumbs, get_issue_user_reports |
partly in event view and feedback list: check, then add flags or commands |
Related: #927 (assignee lookup), #868 (breadcrumbs).
Done when
- The commands land with unit tests, and their parity-table rows in the design are ticked.
- Each command has a permission class and exposure (#1880), if that has landed.
via @BYK.
--
- Dominant language
- TypeScript
- Stars
- 961
- Forks
- 179
- Avg merge
- 15h 33m
- Merged PRs (30d)
- 476
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/toolkit
-
MCP mcp-feedback-pattern
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/toolkit#2276 · 1 comment ·
Maintainers usually reply within 1 day
-
CLI enhancement MCP
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
getsentry/toolkit#1908 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
getsentry/toolkit#1471 · 1 comment ·
Maintainers usually reply within 1 day
-
get_sentry_resource gives no guidance for Explore > Errors list URLsPossibly taken @sentry-junior claimed this today. OpenMCP mcp-feedback-pattern
Difficulty 2/5 1-3 hours Newbie friendliness 32/100
getsentry/toolkit#2278 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
getsentry/toolkit#2275 · 1 comment ·
Maintainers usually reply within 1 day
All issues in getsentry/toolkit
Similar issues
-
Add: BOM CineOpenapproved check:passed streams:add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug platform-android
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Termix-SSH/Mobile#146 · 1 comment ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
devswha/herdr-web-ui#3875 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100