triage-issues

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Triage Issues via Gitee MCP

通过Gitee MCP进行问题分类整理

Batch-process a repository's Issues: classify by priority, add labels, identify duplicates, and generate a clear action list.

批量处理仓库的Issues：按优先级分类、添加标签、识别重复问题，并生成清晰的行动清单。

Prerequisites

前提条件

Gitee MCP Server configured (tools:

list_repo_issues

get_repo_issue_detail

update_issue

comment_issue

)

User must provide: repository owner, repository name
Optional: filter criteria (bugs only / unassigned only / specific milestone, etc.)

已配置Gitee MCP Server（工具：

list_repo_issues

、

get_repo_issue_detail

、

update_issue

、

comment_issue

）

用户必须提供：仓库所有者、仓库名称
可选：筛选条件（仅Bug / 仅未分配 / 特定里程碑等）

Steps

步骤

Step 1: Fetch the Issue List

步骤1：获取问题列表

Use

list_repo_issues

to retrieve open Issues:

```
state
```
:
```
open
```
(open Issues only)
Paginate if there are many Issues (20 per page)

使用

list_repo_issues

获取未关闭的Issues：

```
state
```
：
```
open
```
（仅未关闭的Issues）
若问题数量较多则分页（每页20条）

Step 2: Batch Analysis

步骤2：批量分析

For each Issue, quickly evaluate:

Type classification

```
bug
```
: something is broken, throwing errors, or crashing
```
feature
```
: request for new functionality
```
enhancement
```
: improvement to existing functionality
```
question
```
: usage question
```
docs
```
: documentation-related
```
duplicate
```
: same as an existing Issue

Priority assessment

```
P0 - Critical
```
: affects core functionality, production bug, security vulnerability
```
P1 - High
```
: significant functional defect, affects many users
```
P2 - Medium
```
: general improvement, workaround exists
```
P3 - Low
```
: nice-to-have, cosmetic improvement

Status assessment

Whether there are sufficient reproduction steps (for bugs)
Whether more information is needed
Whether a PR is already addressing it

对每个Issue快速评估：

类型分类

```
bug
```
：功能故障、报错或崩溃
```
feature
```
：新功能请求
```
enhancement
```
：对现有功能的改进
```
question
```
：使用问题咨询
```
docs
```
：文档相关问题
```
duplicate
```
：与现有Issue重复

优先级评估

```
P0 - Critical
```
：影响核心功能、生产环境Bug、安全漏洞
```
P1 - High
```
：严重功能缺陷，影响大量用户
```
P2 - Medium
```
：常规改进，存在替代方案
```
P3 - Low
```
：锦上添花的功能、外观优化

状态评估

是否有足够的复现步骤（针对Bug）
是否需要更多信息
是否已有PR在处理该问题

Step 3: Generate Triage Report

步骤3：生成分类整理报告

Output a structured report:

undefined

输出结构化报告：

undefined

Issue Triage Report

问题分类整理报告

Repository: [owner/repo] Date: [date] Total open issues: [N]

仓库：[所有者/仓库名] 日期：[日期] 未关闭问题总数：[N]

🔴 P0 Critical (needs immediate attention)

🔴 P0 紧急（需立即处理）

#	Title	Type	Note
#N	[title]	bug	[one sentence explaining urgency]

#	标题	类型	备注
#N	[标题]	bug	[一句话说明紧急性]

🟠 P1 High Priority

🟠 P1 高优先级

#	Title	Type	Note

#	标题	类型	备注

🟡 P2 Medium Priority

🟡 P2 中优先级

#	Title	Type	Note

#	标题	类型	备注

🟢 P3 Low Priority

🟢 P3 低优先级

#	Title	Type	Note

#	标题	类型	备注

Needs More Information

需要更多信息

#N [title]: [what information is missing]

#N [标题]：[缺失的信息内容]

Possible Duplicates

可能重复的问题

#N may be a duplicate of #M: [explanation]

#N 可能与 #M 重复：[说明]

Recommended for Closure

建议关闭的问题

#N [title]: [reason, e.g., long inactive / already resolved another way]

undefined

#N [标题]：[原因，例如：长期未活跃 / 已通过其他方式解决]

undefined

Step 4: Update Issue Labels (requires user confirmation)

步骤4：更新Issue标签（需用户确认）

Ask the user whether to automatically update labels and priorities.

After confirmation, use

update_issue

for Issues that need updating:

Add appropriate labels
Update priority
Assign to a team member (if specified by the user)

For Issues that need more information, use

comment_issue

to ask:

Thanks for submitting this issue!

To help us address it more effectively, could you please provide:
- [Missing reproduction steps]
- [Environment and version info]
- [Expected behavior vs. actual behavior]

Thank you!

询问用户是否自动更新标签和优先级。

确认后，对需要更新的Issue使用

update_issue

：

添加合适的标签
更新优先级
分配给团队成员（若用户指定）

对需要更多信息的Issue，使用

comment_issue

发送以下内容：

感谢提交此问题！

为了更高效地处理它，能否请您提供：
- [缺失的复现步骤]
- [环境和版本信息]
- [预期行为与实际行为对比]

谢谢！

Notes

注意事项

Triage focuses on classification and organization — no need to deep-dive into technical details of each Issue
Always confirm with the user before performing bulk updates to avoid unintended changes
If there are more than 50 Issues, consider processing in batches or filtering by a specific label

分类整理的重点是分类和组织——无需深入每个Issue的技术细节
在执行批量更新前务必与用户确认，避免意外变更
若Issue数量超过50个，建议分批处理或按特定标签筛选