R05.11.01.01 · 任务小类

事项与迭代管理

Issue & sprint management

Triage, plan and report issues and sprints.

20 条本项目编写的提案 · 分类 v1.1 · 新增基准运行 0 次。下方验证方式与部分得分规则是设计，不是执行结果。

典型应用: Jira · Linear · Asana
小类 GUI 需求标签: AP · API 足够

数字员工关联

本项目的小类归属，不代表员工能力实证或已导入基准覆盖。验收与价值指标均为建议，未测量 ROI。

关联岗位

项目、研究与协作 · 项目记录、依赖排期、带引用报告、同事确认的信息与无冲突共享协作分别作为结果。

对照全部数字员工工作流设计

任务提案 · 20

展开查看完整原文与建议检查方式；两种界面均保留提案英文原文。

R05.11.01.01-T01 Triage incoming bugs by component, priority and owner

原始指令

Jira Cloud (test site), project MOBILE has 30 untriaged bugs in status 'New'. Using input/triage_matrix.md (severity x user-impact -> priority; keyword -> component; component -> lead), set component, priority and assignee on each and transition it to 'Triaged'. Leave feature requests untouched.

平台: web · 任意系统（网页）
应用: Jira
交互表面: brow · 浏览器 api · API / SDK
GUI 需求 · 任务设定: AP · API 足够
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 type · 文字与表单 code · 代码与命令
工作产物: WP08 · 应用 / 系统状态
条件: 未声明
提案难度: 3 / 5

建议验证方式

REST read of the 30 issues: component, priority, assignee and status equal key; the 4 seeded feature requests unchanged (changelog empty after task start).

建议部分得分

30% components; 30% priorities; 30% assignees and transitions; 10% features untouched.

R05.11.01.01-T02 Plan a sprint to capacity respecting rank and blockers

原始指令

Jira Software (test site), board 'Payments'. Fill Sprint 24 from the top of the ranked backlog up to the team capacity of 42 story points; skip any issue blocked by an unresolved issue outside the sprint, and keep pulling the next ranked issue instead. Set sprint goal 'Ship refunds v2' and start the sprint (2 weeks from 2026-10-19).

平台: web · 任意系统（网页）
应用: Jira
交互表面: brow · 浏览器 api · API / SDK
GUI 需求 · 任务设定: AP · API 足够
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: drag · 拖放 click · 指向与点击 type · 文字与表单
工作产物: WP08 · 应用 / 系统状态
条件: 未声明
提案难度: 4 / 5

建议验证方式

Agile REST: Sprint 24 issue set equals greedy key (rank order, capacity 42, blocker rule); state active, dates and goal exact; no other sprint changed.

建议部分得分

50% correct issue set; 20% points <= 42 and maximal; 20% goal and dates; 10% started.

R05.11.01.01-T03 Close a sprint and carry over unfinished work

原始指令

In Jira (test site), complete Sprint 23 on board 'Payments', moving all incomplete issues to Sprint 24 (not the backlog). Then write the completed story points and the number of carried-over issues to output/sprint23.txt.

平台: web · 任意系统（网页）
应用: Jira
交互表面: brow · 浏览器 api · API / SDK
GUI 需求 · 任务设定: AP · API 足够
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 type · 文字与表单
工作产物: WP08 · 应用 / 系统状态
条件: 未声明
提案难度: 2 / 5

建议验证方式

Sprint 23 state closed; all its non-done issues now in Sprint 24; output values equal key computed from issue status at close.

建议部分得分

40% sprint closed; 40% incomplete issues moved to Sprint 24; 20% numbers reported.

R05.11.01.01-T04 Set up a cycle and estimate its issues in Linear

原始指令

In Linear (test workspace), team 'Platform': create cycle 2026-W43 (2026-10-19..2026-11-01), move the 9 issues labeled 'next-cycle' into it, and set estimates from input/estimates.csv (Fibonacci scale).

平台: web · 任意系统（网页）
应用: Linear
交互表面: brow · 浏览器 api · API / SDK
GUI 需求 · 任务设定: AP · API 足够
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 type · 文字与表单
工作产物: WP08 · 应用 / 系统状态
条件: 未声明
提案难度: 2 / 5

建议验证方式

GraphQL read: cycle with exact dates; the 9 issues in the cycle with estimates per CSV; no other issues moved.

建议部分得分

30% cycle created; 40% issues moved; 30% estimates.

R05.11.01.01-T05 Triage a Linear inbox with duplicate detection

原始指令

Linear (test workspace) Triage inbox holds 24 issues from the support integration. Mark the 6 duplicates as duplicates of the existing issue they repeat, label the rest with one of {bug, ux, perf}, route each to team Web, iOS or Android per input/routing.md, and accept them into Backlog.

平台: web · 任意系统（网页）
应用: Linear
交互表面: brow · 浏览器 api · API / SDK
GUI 需求 · 任务设定: AP · API 足够
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 type · 文字与表单 nav · 平移 / 缩放 / 滚动
工作产物: WP08 · 应用 / 系统状态
条件: 未声明
提案难度: 3 / 5

建议验证方式

Duplicate relations equal key pairs; labels and teams per key for 18 issues; all out of triage. False duplicate links deduct.

建议部分得分

35% duplicates linked correctly; 30% labels; 25% team routing; 10% accepted.

R05.11.01.01-T06 Schedule epics on a Jira Plans timeline across three teams

原始指令

Jira Plans (Advanced Roadmaps, test site) plan 'H1 2027' shows 8 unscheduled epics for 3 teams. Drag epic bars on the timeline so dependencies (arrows) are respected, no team has more than 2 epics in flight at once, and each epic fits its team's sprint capacity. Review and save changes to Jira.

平台: web · 任意系统（网页）
应用: Jira Plans
交互表面: brow · 浏览器
GUI 需求 · 任务设定: G2 · GUI 必要
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: drag · 拖放 nav · 平移 / 缩放 / 滚动 vis · 视觉判断
工作产物: WP08 · 应用 / 系统状态
条件: hidden · 隐藏 / 过期状态
提案难度: 4 / 5

建议验证方式

After save, epic start/due dates via REST: precedence satisfied, <= 2 concurrent per team, story-point sum per sprint <= capacity. Jira API tokens are withheld from the agent account, so dates reach Jira only via the plan's Review changes save; grader reads only committed values.

建议部分得分

35% dependencies respected; 25% concurrency limit; 25% capacity; 15% changes saved to Jira.

R05.11.01.01-T07 Build a team dashboard from a saved JQL filter

原始指令

In Jira (test site), save filter 'Payments open bugs' (project PAY, type Bug, unresolved, priority >= High) and create dashboard 'Payments Health' with: Filter Results (that filter, columns Key/Summary/Priority/Assignee), Two-Dimensional Filter Statistics (Assignee x Priority), and Created vs Resolved chart (30 days).

平台: web · 任意系统（网页）
应用: Jira
交互表面: brow · 浏览器
GUI 需求 · 任务设定: HY · 混合
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 type · 文字与表单 drag · 拖放
工作产物: WP03 · 视觉排版
条件: 未声明
提案难度: 3 / 5

建议验证方式

REST: filter JQL semantically equal (result set equality on seeded data); dashboard exists with 3 gadgets whose configs (filter id, axes, period) match; gadget layout readable via dashboard item properties.

建议部分得分

30% filter correct; 25% results gadget; 25% 2D statistics; 20% created-vs-resolved.

R05.11.01.01-T08 Create an Asana project from a template with sections and rules

原始指令

In Asana (test workspace), create project 'Q4 Webinar' from template 'Event Launch', rename sections per input/sections.txt, and add two rules: when a task moves to 'Review' assign it to the project owner; when marked complete move it to 'Done'.

平台: web · 任意系统（网页）
应用: Asana
交互表面: brow · 浏览器
GUI 需求 · 任务设定: HY · 混合
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 type · 文字与表单 drag · 拖放
工作产物: WP08 · 应用 / 系统状态
条件: 未声明
提案难度: 2 / 5

建议验证方式

Asana API read: project from template, section names/order exact; rules verified behaviorally: grader moves a test task to Review and completes another, then checks assignment and section. Rules have no public API.

建议部分得分

30% project and sections; 35% rule 1 behaves; 35% rule 2 behaves.

R05.11.01.01-T09 Rebalance overallocated work in Asana Workload

原始指令

Asana (test workspace) portfolio 'Brand Refresh' Workload view shows 3 designers over 40 h/week in weeks 44-46. Reassign tasks or move due dates so nobody exceeds 40 h in any week, no task moves past its milestone, and only designers with the 'Illustration' skill tag get illustration tasks.

平台: web · 任意系统（网页）
应用: Asana
交互表面: brow · 浏览器
GUI 需求 · 任务设定: HY · 混合
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: drag · 拖放 vis · 视觉判断 nav · 平移 / 缩放 / 滚动
工作产物: WP08 · 应用 / 系统状态
条件: 未声明
提案难度: 4 / 5

建议验证方式

Task assignee/dates via API: weekly effort per designer <= 40 h (custom field 'Effort h'); due <= milestone date; skill constraint satisfied; changes minimal (<= key + 3 edits).

建议部分得分

45% no overallocation; 25% milestone constraint; 20% skill constraint; 10% minimal edits.

R05.11.01.01-T10 Populate GitHub Projects fields and iterations from a plan

原始指令

GitHub Projects (test org) project 'API v3' has 25 issues. From input/plan.csv set the Iteration field (Iteration 5-7), the single-select 'Area', the number 'Estimate' and status, and create a board view grouped by Iteration and a table view filtered to Area:auth.

平台: web · 任意系统（网页）
应用: GitHub Projects
交互表面: brow · 浏览器 api · API / SDK
GUI 需求 · 任务设定: AP · API 足够
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 type · 文字与表单 code · 代码与命令
工作产物: WP08 · 应用 / 系统状态
条件: 未声明
提案难度: 3 / 5

建议验证方式

GraphQL ProjectV2 read: field values per item equal CSV; two views exist with correct layout, groupBy and filter.

建议部分得分

50% field values; 20% status; 30% two views configured.

R05.11.01.01-T11 Configure sprint capacity and assign work in Azure Boards

原始指令

In Azure DevOps (test org), project 'Retail', create Sprint 12 (2026-10-19..30) for team 'Checkout', set member capacities and days off from input/capacity.xlsx, then assign the 14 backlog items listed in input/sprint12_items.txt so no member exceeds capacity in remaining work.

平台: web · 任意系统（网页）
应用: Azure DevOps Boards
交互表面: brow · 浏览器 api · API / SDK
GUI 需求 · 任务设定: AP · API 足够
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 type · 文字与表单 drag · 拖放
工作产物: WP08 · 应用 / 系统状态
条件: 未声明
提案难度: 3 / 5

建议验证方式

REST: iteration with dates; team capacity per member and days off exact; 14 items in Sprint 12; sum of remaining work per assignee <= capacity x working days.

建议部分得分

20% iteration; 30% capacities and days off; 30% items in sprint; 20% no over-capacity.

R05.11.01.01-T12 Move 120 issues to a new project with field mapping

原始指令

Jira (test site): split project LEGACY by moving its 120 open issues with component 'Billing' into new project BILL. Use the bulk Move wizard, map statuses per input/status_map.csv, map issue type 'Defect' to 'Bug', and preserve sprint, fixVersion where it exists in BILL, and all comments and attachments.

平台: web · 任意系统（网页）
应用: Jira
交互表面: brow · 浏览器
GUI 需求 · 任务设定: HY · 混合
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 nav · 平移 / 缩放 / 滚动
工作产物: WP08 · 应用 / 系统状态
条件: risk · 高风险 / 不可逆
提案难度: 4 / 5

建议验证方式

REST: 120 issues now in BILL (old keys redirect), statuses per map, types mapped, comment and attachment counts unchanged; non-Billing issues remain in LEGACY.

建议部分得分

35% correct issues moved; 25% status mapping; 15% type mapping; 25% comments/attachments preserved.

R05.11.01.01-T13 Report velocity and say-do ratio from sprint reports

原始指令

From Jira board 'Payments' (test site), compute the average completed story points of the last 5 closed sprints and each sprint's say-do ratio (completed / committed at sprint start, excluding scope added later). Write output/velocity.json with per-sprint values and the average.

平台: web · 任意系统（网页）
应用: Jira
交互表面: brow · 浏览器 api · API / SDK
GUI 需求 · 任务设定: AP · API 足够
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: nav · 平移 / 缩放 / 滚动 vis · 视觉判断 code · 代码与命令
工作产物: WP12 · 答案 / 决策
条件: 未声明
提案难度: 3 / 5

建议验证方式

JSON compared to key from sprint changelog (committed at start, added scope excluded): completed points exact, ratios within 0.01, average within 0.1.

建议部分得分

40% completed points; 40% say-do ratios; 20% average.

R05.11.01.01-T14 Create a Linear project with milestones and a status update

原始指令

In Linear (test workspace), create project 'Search Revamp' for team Web with lead, target date 2027-01-29 and 3 milestones from input/milestones.md; link the 17 issues labeled 'search' to the right milestones; post a project update with health 'At risk' summarizing the two blocked issues.

平台: web · 任意系统（网页）
应用: Linear
交互表面: brow · 浏览器 api · API / SDK
GUI 需求 · 任务设定: AP · API 足够
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 type · 文字与表单
工作产物: WP08 · 应用 / 系统状态
条件: 未声明
提案难度: 3 / 5

建议验证方式

GraphQL: project fields, 3 milestones with dates, issue-to-milestone mapping per key, latest project update health atRisk with body naming both blocked issue ids.

建议部分得分

25% project fields; 20% milestones; 35% issue mapping; 20% update.

R05.11.01.01-T15 Cut a release and draft notes from merged pull requests

原始指令

In Jira (test site), create version 'Mobile 3.4' with release date 2026-10-30, set fixVersion on resolved MOBILE issues whose linked GitHub PR (test org repo) was merged into release/3.4, and save release notes grouped by issue type to output/release_notes.md. Do not release the version.

平台: web · 任意系统（网页）
应用: Jira · GitHub
交互表面: brow · 浏览器
GUI 需求 · 任务设定: HY · 混合
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 nav · 平移 / 缩放 / 滚动 multi · 跨应用
工作产物: WP08 · 应用 / 系统状态
条件: multiapp · 多应用
提案难度: 4 / 5

建议验证方式

Version exists unreleased with date; fixVersion set on exactly the key issue set (merged into release/3.4, not main-only); release notes list those keys grouped by type.

建议部分得分

15% version; 50% correct issue set; 25% notes; 10% not released.

R05.11.01.01-T16 Turn a whiteboard story map into ranked epics and stories

原始指令

Miro board 'Checkout story map' (test team) has 5 activity columns and 31 sticky notes in 3 release swimlanes. Create in Jira (test site) one epic per activity and one story per sticky under its epic, with fixVersion R1/R2/R3 from the swimlane, and rank stories in the backlog top-to-bottom as on the board.

平台: web · 任意系统（网页）
应用: Miro · Jira
交互表面: brow · 浏览器
GUI 需求 · 任务设定: HY · 混合
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: vis · 视觉判断 multi · 跨应用 drag · 拖放 type · 文字与表单
工作产物: WP08 · 应用 / 系统状态
条件: multiapp · 多应用
提案难度: 4 / 5

建议验证方式

Jira REST: 5 epics, 31 stories with epic links and fixVersions per key extracted from sticky positions; backlog rank order matches board order (Kendall tau >= 0.9 for full credit).

建议部分得分

20% epics; 35% stories with epics; 25% versions; 20% rank order.

R05.11.01.01-T17 Author Jira automation rules for parents and urgent bugs

原始指令

In Jira (test site), project PAY, create automation rules: (1) when all sub-tasks are Done, transition the parent to 'Ready for QA'; (2) when a Bug is created or updated to priority Highest, send a message to Slack sandbox channel #pay-alerts with key and summary. Enable both.

平台: web · 任意系统（网页）
应用: Jira Automation · Slack
交互表面: brow · 浏览器
GUI 需求 · 任务设定: HY · 混合
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 type · 文字与表单
工作产物: WP08 · 应用 / 系统状态
条件: multiapp · 多应用
提案难度: 4 / 5

建议验证方式

Behavioral test: grader completes sub-tasks of a seeded story and checks parent status; creates a Highest bug and checks a Slack message with key appears within 60 s; both rules enabled. Rule authoring has no public write API.

建议部分得分

45% rule 1 behaves; 45% rule 2 behaves; 10% both enabled and scoped to PAY.

R05.11.01.01-T18 Handle a mass-delete request under the retention policy

原始指令

A Jira (test site) admin request input/cleanup_req.txt asks to delete all issues in project OPS not updated for 2 years. input/retention_policy.md forbids deleting tickets and requires archiving. Perform the policy-compliant action on exactly the matching issues and write output/cleanup.txt with the count and the action taken.

平台: web · 任意系统（网页）
应用: Jira
交互表面: brow · 浏览器 api · API / SDK
GUI 需求 · 任务设定: AP · API 足够
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 type · 文字与表单
工作产物: WP08 · 应用 / 系统状态
条件: clarify · 需要澄清 risk · 高风险 / 不可逆
提案难度: 3 / 5

建议验证方式

No issue deletions in audit log; exactly the key set archived; output names 'archived' and the count. Any deletion scores 0.

建议部分得分

50% no deletions; 35% correct set archived; 15% report.

R05.11.01.01-T19 Migrate an Asana project into Linear with fix-ups

原始指令

Migrate Asana project 'Growth Experiments' (64 tasks, subtasks, comments, attachments) into Linear team Growth using Linear's Asana importer, then fix what the importer drops: map Asana sections to Linear statuses per input/map.md, convert subtasks to sub-issues, and set the 'Experiment owner' custom field values as assignees.

平台: web · 任意系统（网页）
应用: Asana · Linear
交互表面: brow · 浏览器
GUI 需求 · 任务设定: HY · 混合
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: click · 指向与点击 nav · 平移 / 缩放 / 滚动 multi · 跨应用
工作产物: WP08 · 应用 / 系统状态
条件: long · 长流程 multiapp · 多应用
提案难度: 5 / 5

建议验证方式

Linear GraphQL: 64 issues with titles, statuses per map, parent-child relations equal Asana subtask tree, assignees from the custom field, comment counts and attachments preserved.

建议部分得分

25% all tasks imported; 25% statuses; 20% sub-issue hierarchy; 30% assignees, comments and attachments.

R05.11.01.01-T20 Run quarterly capacity planning in Jira Plans

原始指令

In Jira Plans (test site), plan Q1 2027 for 3 teams: 60 issues across 9 epics with estimates, dependencies and team velocities in the plan. Assign issues to sprints and teams on the timeline so that sprint capacity holds, cross-team dependencies precede dependents by >= 1 sprint, and must-have epics (label 'q1-commit') finish by sprint 6. Save to Jira.

平台: web · 任意系统（网页）
应用: Jira Plans
交互表面: brow · 浏览器
GUI 需求 · 任务设定: G2 · GUI 必要
GUI 需求 · 普通权限: G2 · GUI 必要
交互原语: drag · 拖放 nav · 平移 / 缩放 / 滚动 vis · 视觉判断 click · 指向与点击
工作产物: WP08 · 应用 / 系统状态
条件: long · 长流程 hidden · 隐藏 / 过期状态
提案难度: 5 / 5

建议验证方式

Committed sprint/team assignments via REST: capacity per team-sprint, dependency lag, commit-epic deadlines all checked; scope committed >= 90% of key max. Jira API tokens are withheld from the agent account, so plan edits reach Jira only through the Plans save.

建议部分得分

30% capacity holds; 25% dependency lag; 25% commit epics on time; 20% committed scope at least 0.9 of key max.

已有研究映射

以下沿用研究目录中的基准与小类映射，不是逐题标注、执行记录或产品背书。

同工作流族的小类

R05.11.01.02 进度、依赖与资源