update_issue can't change issue priority

未关闭
#2,154 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
74/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript
领域
api, backend

调研方向

Start with packages/mcp-core/src/tools/catalog/update-issue.ts to trace the input schema and handler, then follow the request through packages/mcp-core/src/api-client/client.ts and the referenced Sentry API priority handling. Add priority support to the update path and account for the API's 400 response when the issue type disallows manual priority changes. Done when an agent can set low, medium, or high priority without changing status or assignment, and unsupported issue types return a clear error.

由索引模型根据 Issue 内容生成。

描述

update_issue has no priority input, so agents can't set an issue's priority (low/medium/high) without also changing status or assignment. Reported through MCP user feedback (Cursor, server 0.42.0): an agent asked to set an issue's priority to low was blocked.

  • The input schema has no priority field (packages/mcp-core/src/tools/catalog/update-issue.ts:908-925), and the handler rejects any call without status or assignedTo (update-issue.ts:951-955; hint at :896).
  • ApiService.updateIssue doesn't send priority either (packages/mcp-core/src/api-client/client.ts:4114-4140).
  • The Sentry API already supports it on the issue PUT endpoint: GroupValidator.priority is a ChoiceField over PriorityLevel (getsentry/sentry src/sentry/api/helpers/group_index/validators/group.py:53-60), and update_groups applies it with handle_priority, which also sets priority_locked_at (src/sentry/api/helpers/group_index/update.py:256-270, :1021-1037).
  • The API returns 400 "Cannot manually set priority of one or more issues." for issue types without enable_user_status_and_priority_changes (update.py:257-263).

Feedback: MCP-SERVER-GND

via Sentry.

--

View Session [Sentry]

主要语言
TypeScript
星标
961
派生
179
平均合并
15 小时 33 分钟
30 天内合并 PR
476

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

getsentry/toolkit 的其他 Issue

查看 getsentry/toolkit 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。