Loading

Topics

What is Command by Asana?

Who can use this feature?
EnterpriseEnterprise+

Visit our pricing page for more information.

Command by Asana is an AI-native product development platform for engineering teams. It gives developers, engineering managers, and product managers one place to plan, build, and ship software, with people and coding agents working side by side.

Related articles:

What it does

Command organizes each team's development work into a Teamspace and plans it into cycles automatically, based on how fast the team actually delivers. Instead of asking engineers to estimate every ticket, Command forecasts when tickets and releases are likely to be done, and updates those forecasts as work moves.

Command also connects development work to the tools engineers already use. You can assign tickets to coding agents alongside people, and link pull requests and branches through the GitHub integration, so code activity appears right on the ticket.

Command's AI features help reduce manual planning work: it can draft tickets with acceptance criteria from a spec or meeting notes, generate status reports tailored to different audiences, and flag risks such as missing acceptance criteria. Learn more in AI in Command by Asana.

Key concepts

If you're coming from Jira or Linear, this table shows how Command's building blocks compare.

 

Command

What it is

Similar to

Teamspace

Your team's home in Command, with its tickets, cycles, releases, and workflow settings.

Jira project / Linear team

Ticket

A single piece of development work, assigned to a person or a coding agent.

Jira issue / Linear issue

Cycle

A recurring period, such as one or two weeks, that Command fills with work based on your team's pace.

Sprint / Linear cycle

Release

A group of tickets working toward a shared ship date.

Jira epic / Linear project

How planning works in Command

  • No story points. Command forecasts delivery dates for tickets and releases from how long your team's recent work took, shown as a range from optimistic to conservative.
  • Priorities drive the plan. Your team orders tickets by priority, and Command decides what fits into each cycle.
  • Stuck work stands out. Tickets that stay in a stage much longer than usual are highlighted, so your team can help unblock them.
Note iconNote

Learn more: Plan work with cycles in Command and Forecasts in Command

How it connects to Asana

Command is built on the Asana Work Graph, so development work stays connected to the rest of your organization's work.

You can add releases to portfolios alongside regular Asana projects. This lets product, marketing, sales, and leadership see how releases are tracking in the context of a larger initiative, such as a product launch, without opening a Teamspace or asking engineers for updates.

How to navigate Command

When you open Command from the sidebar, you go to your team's Teamspace. Tickets move through these stages:

  • Triage – review and sort incoming work.
  • Backlog – prioritized work that isn't planned into a cycle yet.
  • Cycles – planned work, listed as In review, In progress, and Not started, so work closest to done appears at the top.
  • Completed – work that has shipped.

From the Teamspace, you can also open Releases and Teamspace settings, where you manage your team's workflow and GitHub connection.

Who Command is for

Command is built for everyone involved in shipping software. Developers get the context they need on each ticket and see code and agent activity alongside their work. Engineering managers and tech leads run stand-ups from live work in progress and get delivery forecasts without asking the team to estimate. Product managers prioritize work and see realistic dates for releases, while engineering leaders and other stakeholders can follow how releases are progressing across teams, directly in Asana.

Loading
What is Command by Asana? | Asana Help Center