Work · Module
Issues & Sprints
Backlogs, sprints and releases linked to code, support tickets and product decisions
Issues & Sprints runs software and product delivery: backlog, issues, epics, sprints, boards and releases linked to code, support tickets and product decisions. Humans and coding agents work on the same issues, and it is planned as a Work add-on or a standalone subscription.
What it does
Issues & Sprints is planned for W3. Its MVP has a clear exit test: the One3 team migrates its own backlog into it. A standalone subscription includes teams, members, components and a minimal project container without Projects' templates, Gantt or client features.
Core delivery
- Issues with configurable types (bug, story, task, spike), readable keys per team such as WEB-123, priority, bug severity, points or hours estimates, labels, components, attachments, watchers and links such as blocks, relates and duplicates.
- Team workflows with statuses mapped to system categories, transitions with conditions and required fields, and WIP limits.
- Backlog ranking by drag or keyboard, a grooming view with estimates and bulk edit.
- Sprints planned with capacity, a sprint goal and carry-over choices at completion. Capacity uses the same leave-aware availability as Timesheets & PSA.
- Scrum and Kanban boards with swimlanes and quick filters.
- Epics across teams with progress roll-up, and releases with readiness by open severity and a release notes draft.
- Agile charts: burn-down, burn-up, velocity, cycle and lead time and cumulative flow.
Linked to code and support
GitHub and GitLab connectors link branches, commits and pull requests by issue key, show check status and can apply rules such as moving an issue to done when its PR merges. Helpdesk bug links connect tickets to issues, and requesters are notified through Service Desk when the fix is released.
Agents with human primary assignees
Coding-agent delegation lets a team hand an issue to a tenant-connected coding agent through MCP Hub or the API as a contributor while a human stays primary assignee. The agent's activity and PRs show on the issue. A public API and MCP tools give external agents parity, and R3 Actions are still approved in One3.
GA additions
Planned GA work includes sprint planning proposals from the AI Scrum Master, stand-up summaries and blocker alerts, cross-team planning, component ownership and triage rules, bug SLAs linked to Status Page incidents, a Jira Data Center importer ahead of its end of life, time and capitalisation tags, restricted security issues excluded from AI training, release notes publishing to the Help Center changelog after approval, Git-based automation, native mobile and sprint retrospectives. DORA metrics, flag and experiment links, test management lite and incident post-mortems follow in W4.
Features
What Issues & Sprints includes
Issues
Configurable types, team keys, priority, severity, estimates, labels, components and links.
Team workflows
Statuses mapped to categories, conditional transitions, required fields and WIP limits.
Backlog
Ranked backlog with drag or keyboard reorder, grooming view and bulk edit.
Sprints
Capacity-based planning, sprint goal and carry-over choices.
Boards
Scrum and Kanban boards with swimlanes and quick filters.
Epics and releases
Cross-team epics with roll-up; versions with readiness and release notes drafts.
Code linking
GitHub and GitLab branches, commits and PRs by issue key, with check status and transition rules.
Helpdesk bug links
Ticket to issue links with requester notification on release.
Agile charts
Burn-down, burn-up, velocity, cycle and lead time and cumulative flow.
Duplicate detection
AI duplicate suggestions at creation and in triage with similarity explanations.
Importers
Jira Cloud and Linear via API and CSV for others; Jira Data Center importer at GA.
Coding-agent delegation
Delegate to a connected coding agent while a human stays primary assignee.
Bug SLAs and restricted security issues
Response and fix targets by severity; restricted issues excluded from AI training (GA).
Sprint retrospectives
Retros with optional anonymous cards, dot votes and action items as issues (GA).
Workflow
Idea to release delivery loop
- 1
A feature from Product Management becomes an epic with child issues
- 2
Issues are ranked in the backlog
- 3
The team accepts a sprint plan proposal
- 4
A human or coding-agent contributor works the issue and links a PR
- 5
Human review and merge in the code host moves the issue to done
- 6
The release is checked for readiness and notes are published after approval
- 7
Linked tickets get customer update proposals; rollout can go behind a feature flag
AI
AI skills and Digital Employees
Duplicate detection
Suggests likely duplicates with explanations.
Triage suggestions
Suggests type, component, priority and severity.
Sprint plan proposal
Proposes scope with inclusion and exclusion reasons.
Stand-up summaries and blocker alerts
Summarises daily changes and flags aging blockers.
Release notes drafts
Drafts notes from customer-facing issues for approval.
Bug report PII detection
Warns reporters about personal data and suggests redaction.
Digital Employees that use this module
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
Can I use Issues & Sprints without the rest of Work?
Yes, a standalone subscription is planned with its own seat pool and a thin core of teams, members and components.
Can coding agents work on our issues?
Yes, planned. A connected coding agent can be a contributor through MCP Hub or the API while a human stays primary assignee, and its activity and PRs show on the issue.
Can we move from Jira or Linear?
Importers for Jira Cloud and Linear are planned for the MVP, with a Jira Data Center importer at GA, subject to each source's API and export terms.
See Issues & Sprints in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.