菜单
Guide bug tracking workflows including creation, triage, severity classification, and resolution in P4 Plan QA. Use when user mentions bugs, defects, QA, triage, severity, quality assurance, create bug, or fixing issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Author HTML-formatted comments and multiline field values that render correctly in both the Qt desktop client and the React web client. Use when posting/editing comments, setting Multiline Text custom fields, or writing detailedDescription/stepsToReproduce on a Bug.
Guide custom field management, configuration, and usage in P4 Plan. Use when user mentions custom fields, custom columns, metadata, tags, categories, or project-specific data.
Format @user mentions inside HTML comments and multiline fields so they render as a proper link in both the Qt desktop client and the React web client. Use when the user wants to ping someone, notify a teammate, address @-name, or reference a user inside a comment / description / steps to reproduce.
Manage tasks, status updates, assignments, comments, and attachments in P4 Plan. Use when user mentions tasks, status, updates, assignments, my work, todo list, assign, comments, attachments, or collaboration.
Guide backlog refinement sessions, story refinement, estimation, and prioritization in P4 Plan. Use when user mentions backlog, refinement, estimation, story points, or prioritization.
Guide Gantt chart scheduling, scheduled tasks, dependencies, and timeline planning in P4 Plan. Use when user mentions Gantt, scheduling, timeline, dependencies, duration, start date, end date, or waterfall.
| name | p4-plan-bug-tracking |
| description | Guide bug tracking workflows including creation, triage, severity classification, and resolution in P4 Plan QA. Use when user mentions bugs, defects, QA, triage, severity, quality assurance, create bug, or fixing issues. |
Bugs are tracked in the Quality Assurance section. Use the project's qaID (from get_project) when creating bugs.
| User Intent | Tool | Key Parameters |
|---|---|---|
| Create a bug | create_item | type: "bug", projectId, name, severity, detailedDescription, stepsToReproduce |
| Find bugs | search_tasks | findQuery, projectId (use QA section ID) |
| Get bug details | get_tasks | taskIds |
| Set severity | update_item | itemId, severity (A/B/C/D) |
| Set priority | update_item | itemId, priority |
| Assign bug | update_item | itemId, assignedTo: [{ userID }] |
| Start work on bug | start_task | taskId |
| Resolve bug | complete_task | taskId |
| Add discussion | post_comment | taskId, text |
| List attached files | get_attachments | taskId |
| View screenshot/file | download_attachment | taskId, path (from get_attachments) |
| Commit bug to sprint | commit_to_sprint | taskId, sprintId |
| Get team for assignment | list_project_users | projectId |
Bugs with a committedToProjectID are already committed to a sprint. Before modifying, moving, or breaking down committed bugs, always confirm with the user first.
