Keep the plan close.
And the work moving.

No. Teams can work from a kanban board and issue list, then use sprints when a time-boxed planning rhythm is useful. Start with the views and statuses your team needs instead of recreating every part of an old process.

Not yet. The web import screen lists Jira, Trello, Asana, CSV, and JSON as planned sources, but project imports are not currently available.

Planner starts with familiar agile types: Epic, Story, Task, Bug, and SubTask. Other templates set up types for client work, DevOps, support, marketing and sales instead, and teams can add or rename types, choose icons, change default estimates, and link each type to a workflow in project settings. Teams can use sprints or continuous kanban flow.

Yes. In project settings, edit an issue type to choose from a curated vector icon library. It covers sales, design, finance, construction, marketing, and other common business workflows, including New Business, Upsell, and Renewal. Saved choices appear beside those issue types in Planner. Reset the icon to return to its default; the familiar agile icons remain available. The library keeps icons consistent across workspaces and light and dark themes.

Yes. Each issue type links to a workflow, and status changes are validated against the allowed transitions in that workflow. New projects start from a template (developer, simple, client agency, DevOps, support, marketing or sales) that sets up their issue types and workflows. People who can edit the project can add issue types and change workflow stages from project settings, and tickets in a removed stage are moved to another stage.

The board shows how work is moving and can group it by status, owner, type, or priority. The backlog helps you refine future work and plan sprints. The roadmap shows standalone issues and parent-child work against dates across your project’s issue types. It starts with the current project selected; clear the project filter to see accessible projects in clearly labeled groups. Move or resize a date range, schedule work without dates, and use search, status filters, or a different time scale to focus the plan. All three lead back to the same issue and its context.

On large boards, open Board overview beside the Board/List selector to see a minimap of your horizontal position and jump across columns. On long grouped lists, Jump to group shows group names and issue counts, marks the current group, and lets you jump to another section or the top or bottom. A group jump closes the panel and preserves collapsed groups. Both controls reflect the current grouping and filters and appear only when the view is large enough to need them.

Unfinished issues stay assigned to their sprint; they are not automatically moved to the backlog or another sprint. Review them and choose where they belong. The REST API (Preview) allows a sprint to be marked complete even when issues remain open, so do not rely on a completion gate.

Sprint creation, names, dates, and issue assignment are available in the web backlog. Its start and complete controls do not yet save those status transitions. Persisted sprint status changes are available through the REST API (Preview).

Planner remembers relevant filters and view preferences between visits, scoped to the project, workspace, or member. The current web experience does not provide named, shareable saved views.

With a configured AI provider, you can review suggested subtasks for an issue and use AI Assist inside comments to draft replies, summarize discussions, or find next steps. You choose what to keep before turning suggestions into work or posting a comment.

The REST API (Preview) supports worklog entries and read-only release version data. A web worklog entry interface and full web release management are not currently available. The page marks these separately from the interactive planning features.