R05.11.01.01 · TASK CLASS

Issue & sprint management

Triage, plan and report issues and sprints.

20 project-authored proposals · taxonomy v1.1 · 0 new benchmark runs. Verifiers and partial-credit rules below are designs, not executed results.

Typical applications: Jira · Linear · Asana
Class GUI-need label: AP · API-sufficient

Digital-employee context

Project class assignments, not demonstrated employee capability or imported benchmark coverage. Acceptance criteria and value metrics are proposals; no ROI has been measured.

Related roles

Projects, research and collaboration · Project records, dependency schedules, cited reports, confirmed colleague input and conflict-free shared work are distinct outcomes.

Compare all digital-employee workflow designs

Task proposals · 20

Expand to inspect the complete original wording and proposed checks. Original proposal text remains English in both interfaces.

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Jira
Interfaces: brow · Browser api · API/SDK
GUI need · task setting: AP · API-sufficient
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click type · Text & forms code · Code & commands
Work product: WP08 · App/system state
Conditions: None declared
Proposed difficulty: 3 / 5

Proposed verifier

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

Proposed partial credit

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

Original instruction

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).

Platforms: web · Any OS (web)
Applications: Jira
Interfaces: brow · Browser api · API/SDK
GUI need · task setting: AP · API-sufficient
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: drag · Drag & drop click · Point & click type · Text & forms
Work product: WP08 · App/system state
Conditions: None declared
Proposed difficulty: 4 / 5

Proposed verifier

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.

Proposed partial credit

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Jira
Interfaces: brow · Browser api · API/SDK
GUI need · task setting: AP · API-sufficient
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click type · Text & forms
Work product: WP08 · App/system state
Conditions: None declared
Proposed difficulty: 2 / 5

Proposed verifier

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

Proposed partial credit

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

Original instruction

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).

Platforms: web · Any OS (web)
Applications: Linear
Interfaces: brow · Browser api · API/SDK
GUI need · task setting: AP · API-sufficient
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click type · Text & forms
Work product: WP08 · App/system state
Conditions: None declared
Proposed difficulty: 2 / 5

Proposed verifier

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

Proposed partial credit

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

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Linear
Interfaces: brow · Browser api · API/SDK
GUI need · task setting: AP · API-sufficient
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click type · Text & forms nav · Pan/zoom/scroll
Work product: WP08 · App/system state
Conditions: None declared
Proposed difficulty: 3 / 5

Proposed verifier

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

Proposed partial credit

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Jira Plans
Interfaces: brow · Browser
GUI need · task setting: G2 · GUI-essential
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: drag · Drag & drop nav · Pan/zoom/scroll vis · Visual judgment
Work product: WP08 · App/system state
Conditions: hidden · Hidden/stale state
Proposed difficulty: 4 / 5

Proposed verifier

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.

Proposed partial credit

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

Original instruction

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).

Platforms: web · Any OS (web)
Applications: Jira
Interfaces: brow · Browser
GUI need · task setting: HY · Hybrid
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click type · Text & forms drag · Drag & drop
Work product: WP03 · Visual layout
Conditions: None declared
Proposed difficulty: 3 / 5

Proposed verifier

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.

Proposed partial credit

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

Original instruction

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'.

Platforms: web · Any OS (web)
Applications: Asana
Interfaces: brow · Browser
GUI need · task setting: HY · Hybrid
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click type · Text & forms drag · Drag & drop
Work product: WP08 · App/system state
Conditions: None declared
Proposed difficulty: 2 / 5

Proposed verifier

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.

Proposed partial credit

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

R05.11.01.01-T09 Rebalance overallocated work in Asana Workload

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Asana
Interfaces: brow · Browser
GUI need · task setting: HY · Hybrid
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: drag · Drag & drop vis · Visual judgment nav · Pan/zoom/scroll
Work product: WP08 · App/system state
Conditions: None declared
Proposed difficulty: 4 / 5

Proposed verifier

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).

Proposed partial credit

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: GitHub Projects
Interfaces: brow · Browser api · API/SDK
GUI need · task setting: AP · API-sufficient
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click type · Text & forms code · Code & commands
Work product: WP08 · App/system state
Conditions: None declared
Proposed difficulty: 3 / 5

Proposed verifier

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

Proposed partial credit

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

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Azure DevOps Boards
Interfaces: brow · Browser api · API/SDK
GUI need · task setting: AP · API-sufficient
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click type · Text & forms drag · Drag & drop
Work product: WP08 · App/system state
Conditions: None declared
Proposed difficulty: 3 / 5

Proposed verifier

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.

Proposed partial credit

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Jira
Interfaces: brow · Browser
GUI need · task setting: HY · Hybrid
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click nav · Pan/zoom/scroll
Work product: WP08 · App/system state
Conditions: risk · Irreversible/risky
Proposed difficulty: 4 / 5

Proposed verifier

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.

Proposed partial credit

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Jira
Interfaces: brow · Browser api · API/SDK
GUI need · task setting: AP · API-sufficient
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: nav · Pan/zoom/scroll vis · Visual judgment code · Code & commands
Work product: WP12 · Answer/decision
Conditions: None declared
Proposed difficulty: 3 / 5

Proposed verifier

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

Proposed partial credit

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

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Linear
Interfaces: brow · Browser api · API/SDK
GUI need · task setting: AP · API-sufficient
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click type · Text & forms
Work product: WP08 · App/system state
Conditions: None declared
Proposed difficulty: 3 / 5

Proposed verifier

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.

Proposed partial credit

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Jira · GitHub
Interfaces: brow · Browser
GUI need · task setting: HY · Hybrid
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click nav · Pan/zoom/scroll multi · Cross-app
Work product: WP08 · App/system state
Conditions: multiapp · Multi-app
Proposed difficulty: 4 / 5

Proposed verifier

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.

Proposed partial credit

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Miro · Jira
Interfaces: brow · Browser
GUI need · task setting: HY · Hybrid
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: vis · Visual judgment multi · Cross-app drag · Drag & drop type · Text & forms
Work product: WP08 · App/system state
Conditions: multiapp · Multi-app
Proposed difficulty: 4 / 5

Proposed verifier

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).

Proposed partial 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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Jira Automation · Slack
Interfaces: brow · Browser
GUI need · task setting: HY · Hybrid
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click type · Text & forms
Work product: WP08 · App/system state
Conditions: multiapp · Multi-app
Proposed difficulty: 4 / 5

Proposed verifier

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.

Proposed partial credit

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Jira
Interfaces: brow · Browser api · API/SDK
GUI need · task setting: AP · API-sufficient
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click type · Text & forms
Work product: WP08 · App/system state
Conditions: clarify · Ask when unclear risk · Irreversible/risky
Proposed difficulty: 3 / 5

Proposed verifier

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

Proposed partial credit

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

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Asana · Linear
Interfaces: brow · Browser
GUI need · task setting: HY · Hybrid
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: click · Point & click nav · Pan/zoom/scroll multi · Cross-app
Work product: WP08 · App/system state
Conditions: long · Long-horizon multiapp · Multi-app
Proposed difficulty: 5 / 5

Proposed verifier

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.

Proposed partial credit

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

Original instruction

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.

Platforms: web · Any OS (web)
Applications: Jira Plans
Interfaces: brow · Browser
GUI need · task setting: G2 · GUI-essential
GUI need · ordinary access: G2 · GUI-essential
Interaction primitives: drag · Drag & drop nav · Pan/zoom/scroll vis · Visual judgment click · Point & click
Work product: WP08 · App/system state
Conditions: long · Long-horizon hidden · Hidden/stale state
Proposed difficulty: 5 / 5

Proposed verifier

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.

Proposed partial credit

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

Mapped research references

Existing benchmark-to-class links from the research catalog. They are not record-level annotations, executions or product endorsements.

In this workflow family

R05.11.01.02 Schedules, dependencies & resources