Sprints, fields and archiving
Sprints
With sprints on (the Scrum template, or an owner turns them on in Settings and access), the Backlog and sprints tab plans the work:
- New sprint plans one, with a name, a goal and dates.
- Move to… on a task puts it in a sprint, or back in the backlog. A new task can go straight into a sprint.
- Start runs a planned sprint; one runs at a time, and the board shows it.
- Complete finishes the running sprint. Its unfinished tasks go to the next planned sprint, or back to the backlog.
Without sprints the tab is a List of the open tasks.
Above the lists are the same search and filters as on the board (assignee, type, epic). Each list shows its first 50 tasks with Show 50 more under it; its heading counts and adds up the estimates of all of them (or all that match).
Fields of the project's own
Owners add fields under Settings and access → Fields: text, a number, a choice, choices, a date or a person (someone with access to the project). They show on every task of the project, can be filtered on through the API, and are in exports and webhooks.
Archiving
Archive project (owners) makes it read-only and takes it out of the list and the sidebar; its tasks, comments and history stay. Archived on the projects page lists them, and an owner can Restore one. Export as JSON downloads everything in the project: settings, access, tasks with comments and history.
AI assistants and the API
With the plugin on, API tokens and AI assistants can be given:
| Permission | Scope |
|---|---|
| Read dev projects | dev:read |
| Change dev tasks | dev:write |
| Manage dev projects | dev:admin |
Assistants then get tools to list and read projects, who has access and tasks, create and change tasks, plan sprints, and (as an owner) change a project's columns, fields and access (MCP server, the API). They see the projects you do, with your role.