Compare
Engineering work needs more than a task list.
When the work is bugs and sprints, you need technical issue detail: keys, links, severity, estimates and history. Nothing Left is an open-source tracker for engineering teams that plan in project sprints and want their notes and their AI agent in the same place.
A technical home for bugs, sprints and the notes behind them.
Follow ACME-12 from the first report, through a sprint, to the decision record and runbooks beside it. Every step changes the same issue, and its history records who changed what.
1 / 5Filed · Casey Kim, 2 Oct 2026, 9:05am
Casey Kim files the bug with steps to reproduce. It gets a key at once, ACME-12.
Invite link blank after it expires
Steps. Open an invitation link that is older than seven days.
Expected. A message that the link has expired and a way to request a new one.
Actual. A blank page.
- Reporter
- Casey Kim
- Assignee
- Unassigned
- Severity
- High
- Sprint
- Unscheduled
Casey Kim created ACME-122 Oct 2026, 9:05am
2 / 5Planned into a sprint · 3 Oct 2026, 10:14am
It joins Sprint 08 with story points, an owner, an estimate and a due date.
Sprint 08
Make invitations clearer
4 Oct – 17 Oct 2026
ACME-12Invite link blank after it expires
- Assignee
- Alex Lee
- Story points
- 3
- Estimation
- 2h
- Due date
- 9 Oct 2026
Casey Kim · Assignee: Unassigned → Alex Lee, Estimation: 2h, Due date: 9 Oct 20263 Oct 2026, 10:14am
Casey Kim · Sprint: Sprint 08, Story points: 33 Oct 2026, 10:14am
3 / 5Linked and worked · 6 Oct 2026, 9:20am
A dependency, a subtask and a severity change, each in the history.
Invite link blank after it expires
Depends on
ACME-4Invite expiry setting per org
Parent for
ACME-13Invite expiry date shown in UTC
- Status
- In Progress
- Spent time
- 20m of 2h
Alex Lee · linked: depends on ACME-45 Oct 2026, 11:28am
Alex Lee · Severity: High → Critical5 Oct 2026, 11:30am
Alex Lee · linked: parent for ACME-135 Oct 2026, 11:34am
Alex Lee · Status: Open → In Progress6 Oct 2026, 9:20am
4 / 5Fixed inside the sprint · 8 Oct 2026, 4:40pm
Fixed is a done status, so the sprint counts its points.
Invite link blank after it expires
- Status
- Fixed
- Spent time
- 1h 45m of 2h
- Sprint
- Sprint 08
Sprint 08 at the end of 8 Oct 2026: 12 of 34 points done
5 / 5The notes behind it · decision record published 2 Oct 2026
The decision record sits in the project’s knowledge base, next to the runbooks.
- Decisions
- Invitation links and expiry
- Runbooks
- Restoring a failed sync
Decision record
Invitation links and expiry
article://ACME/invitation-links-and-expiry
- Author
- Alex Lee
- References
- ACME-12
Invite link blank after it expires
Open ACME-12 and the record is listed under Referenced by. Runbooks work the same way: Sam Ortiz’s Restoring a failed sync references ACME-24, Partner sync stops after a key rotation, so whoever opens that issue finds the steps.
Hand-drawn product views with fictional data. More on engineering teams
Nothing Left and Asana, row by row.
Each Asana cell links to Asana’s own page; each Nothing Left cell links to its manual. Nothing Left has no Asana-style intake forms, portfolios or goal management, and the rows say so.
Asana column last verified against its own pages on . Product names are trademarks of their owners.
Show
| Capability | Nothing Left | Asana |
|---|---|---|
| Planning | ||
| Issue keys and links | YesEvery issue gets a key such as ACME-12 that never changes. Links read from both ends: relates to, depends on, duplicates, subtask of.Issues manual | YesReadable IDs come from an ID custom field with a prefix you choose, numbered for tasks and one level of subtasks. Tasks connect through blocking and blocked-by dependencies.ID custom fields |
| Sprints and backlog | YesSprints are planned, started and finished with a goal and dates. An ordered backlog, story points, and a choice of where unfinished issues go when a sprint ends.Sprints manual | LimitedSprint templates and board views, with story points as a custom number field and backlogs sorted through saved views and rules.Agile management |
| Portfolios | NoNo layer above projects. Reports can span projects, but there is no portfolio to group and track them.Reports manual | YesGroup projects to watch their status in one place, with dashboards and roll-ups such as time and budget. Advanced plan and up.Portfolios |
| Cross-team goals | NoA sprint carries a goal. There are no organisation, team or personal goals.Sprints manual | YesCompany, team and personal goals with sub-goals, linked to projects and portfolios, updating as work moves. Advanced plan and up.Goals |
| Intake forms | NoMembers file issues in the app or through an agent. There are no forms for people outside the project.Issues manual | YesForms with conditional questions that anyone with the link can submit; each response becomes a task. Starter plan and up.Forms |
| Workload and capacity | LimitedEstimates, logged time, a time report and an issues-per-assignee report. No capacity view.Reports manual | YesA workload view of each person’s effort across projects, with capacity limits and drag-to-rebalance. Advanced plan and up.Workload |
| Delivery | ||
| Reports | YesNine reports, including a burndown recorded nightly, a Gantt chart, a time report and timesheets. Each exports as CSV.Reports manual | YesProject dashboards from Starter; portfolio dashboards and universal reporting from Advanced. Column, line, burn-up and other charts.Reporting |
| Docs and project knowledge | YesA private knowledge base per project: runbooks and decision records in a tree. An issue key in an article links both ways.Knowledge base manual | LimitedEach project has an Overview and a rich-text Project Brief for shared context, links and embeds.Project Overview and Brief |
| Workflow automation | LimitedStatus rules fired by git events, resolved subtasks and duplicate links, not a general rules engine, and no transition rules: any status can follow any status. An agent can make bulk changes you ask for.Automations manual | YesRules with triggers and actions from Starter, across projects and with apps; AI Studio adds no-code AI workflows.Rules |
| Agents | ||
| MCP server | YesPart of the API. The agent acts as the person who created its token, within their role, using keys and names rather than IDs.MCP manual | YesGenerally available over OAuth for Claude, ChatGPT, Cursor, VS Code and other clients; reads and manages tasks and projects.MCP server |
| AI inside the app | NoNo built-in assistant. Bring the agent you already use and connect it over MCP.MCP manual | YesAI Teammates, AI Studio for no-code AI workflows, and Asana Dash.Asana AI |
| Hosting and pricing | ||
| Self-hosting and source | YesAGPL-3.0 code, the same build as the hosted service, with seat and storage limits as settings. Guides for Docker Compose and AWS.Self-hosting guide | NoCloud service. Its pricing page says it does not plan to offer an internally hosted version; data residency is an enterprise option.Pricing FAQ |
| Admin and governance | LimitedFive fixed roles, scoped agent tokens and two-factor sign-in. No custom roles and no admin console.Permissions | YesSAML, SCIM, audit log, admin app management and SIEM APIs on enterprise plans.Enterprise |
| Plan and price | YesNo subscription charge during beta, for any team size. The first 20 members stay free once billing exists.Pricing | LimitedA free Personal plan for one or two people; Starter, Advanced and Enterprise tiers are paid. Prices are on its pricing page.Pricing |
- Yes
- Built in and documented.
- Limited
- Present, with a narrower scope than the row suggests; the note says how.
- Planned
- Not available today; on the public roadmap or announced.
- No
- Not available.
Where Asana is the stronger tool.
Asana is built for work that crosses departments, and it is not only a task list: it documents engineering workflows, AI features and its own MCP server. Each point below links to Asana’s own page.
Asana MCP serverCross-functional planning
Portfolios and timelines give one view of many projects, and its product-team pages tie roadmaps to strategy across departments.
Asana for product teamsGoals that roll up
Company, team and personal goals link to the projects and portfolios behind them and update as work moves.
GoalsIntake forms
Requests arrive through forms with conditional questions, from people inside or outside the organisation, and land as tasks.
FormsWorkload
Capacity across people and projects, with limits and drag-to-rebalance, over days to years.
WorkloadEnterprise governance
SAML, SCIM, audit logs, service accounts, admin app management and data residency on enterprise tiers.
EnterpriseEngineering workflows, AI and MCP
Bug tracking, sprint templates and integrations with GitHub, GitLab and Jira; AI Teammates and AI Studio; and a generally available MCP server.
Asana for engineering
What Nothing Left does not have
No Asana-style forms, portfolios or goal management. If your team depends on these, keep them in Asana or choose Asana.
- Intake forms that people outside a project can submit
- Portfolios that group projects
- Organisation, team or personal goals
- A workload or capacity view
- General rules that change work automatically; automations here only set a status
- An AI assistant inside the app
Can we run it ourselves?
Yes, and it is a real commitment. Nothing Left is open source under AGPL-3.0, and the hosted beta runs the same build. Running it yourself means the infrastructure and its maintenance are your team’s responsibility, not ours. The guides cover Docker Compose on one machine and AWS.
Asana is a cloud service; its pricing page says it does not plan to offer an internally hosted version. Asana pricing FAQ
- What you run
- The web app and one API process that also serves MCP, with PostgreSQL, Redis and S3-compatible storage beside them.
- What stays the same
- The same AGPL-3.0 build as the hosted service. Seat and storage limits are environment settings you can change.
- What is yours to keep running
- Upgrades and migrations, backups of the database and buckets, email delivery, sign-in apps, security patches and uptime.
Which one fits your team?
Asana is likely the better choice for organisation-wide programs and for departments outside engineering. Nothing Left is narrower on purpose: a tracker for the engineering and product work itself.
Choose Asana if…
- You plan organisation-wide programs that span marketing, operations, design and engineering.
- Non-technical departments need intake forms, approvals and goals in the same tool as the developers.
- Leadership tracks portfolios and company goals across many teams.
- You need SAML, SCIM, audit logs and data residency on day one.
- You want AI built into the app and rule-based automation without writing anything.
Choose Nothing Left if…
- The work is mostly bugs, features and sprints, and engineers want keys they can type.
- Sprints, backlog order, story points and a nightly burndown should be built in, not assembled from templates.
- Runbooks and decision records should live beside the issues they explain.
- Your team uses its own AI agent and wants it to work through the same permissions as a person.
- You want the source under AGPL-3.0 and the option to run it on your own infrastructure.
Moving work across.
There is no native Asana importer. There are two paths: a generic CSV import for the bulk of it, and an agent you guide, with every mapping reviewed before anything is written.
Export from Asana
Asana exports a project as CSV from its project actions menu: names, assignees, dates, tags, notes and parent tasks.
Export to CSVImport the CSV
Generic CSV import is the dependable bulk path. There is no native Asana importer.
Or let an agent carry it across
An agent connected to both tools can read open tasks and create projects, tags and issues here through MCP. You review the field mapping, duplicates, attachments and people before it writes.
Compare your Asana bill.
Asana is selected, starting from its lowest paid plan. Replace that with what your team pays today and see what the beta takes off it. Nothing you type leaves this page.
The calculator is not available in this browser right now. Reloading the page may bring it back. The short version: during beta the subscription is zero, whatever you pay today.
Currently using
Check your plan on Asana's pricing pageUse the figure on your latest invoice.
Currency
You know
Digits only, such as 1250, 1,250.50 or 1.250,50.
Filled in from Asana's lowest paid plan: US list price, billed monthly, checked 11 Oct 2026. Higher plans cost more, and annual or volume pricing differs. Replace it with your invoice figure.
- Current subscription spend
- -
- Nothing Left subscription during beta
- $0
- Illustrative subscription spend avoided during beta if you replace and cancel the current plan
- -
Monthly subscription only, in the currency you chose, with no exchange conversion. Filled-in prices are US list prices for each tool's lowest paid plan, billed monthly, checked 11 Oct 2026; they apply in USD only. Migration effort, add-ons, storage and any future seat pricing are outside this comparison. Product names are trademarks of their owners.
Questions teams ask before leaving Asana.
About fit, agents, hosting and moving work. Short answers here, details in the docs.
Is Nothing Left a full replacement for Asana?
Not for every team. It has no intake forms, portfolios, goals, workload view, rules or built-in AI. It is a tracker for engineering and product work: issues with keys and links, sprints and a backlog, reports, project knowledge and an MCP server. See the comparison
Does Asana have an MCP server too?
Yes. Asana documents a generally available MCP server that clients such as Claude, ChatGPT and Cursor connect to over OAuth. In Nothing Left, MCP is part of the API, and every tool acts as the person who created the token, within their role. Asana’s MCP documentation
Can we self-host Nothing Left?
Yes. The code is AGPL-3.0 and a self-hosted install runs the same build as the hosted service. Your team runs and maintains it: upgrades, backups, email and uptime. Install guides cover Docker Compose and AWS. Self-hosting
How do we move our work from Asana?
Use the generic CSV import. An agent connected to both tools can also carry open tasks across through MCP, with you reviewing the mapping. There is no native Asana importer.
Can engineering use Nothing Left while the rest of the company stays in Asana?
Yes. Nothing Left does not need the whole organisation, and it does not sync with Asana. The engineering team keeps its issues, sprints and runbooks here; programs and goals stay where they are. For engineering teams
What does it cost?
No subscription charge during beta, for any team size. When billing arrives, the first 20 members of every organisation stay free, and we will give notice before charging for more. Pricing
Bring one engineering project across.
Join the beta, create a project and file the bug you are working on now. Your other teams can stay where they are.
@caseyreproduced with a ten-day-old link. The log shows the token check returning before the page renders. The fix waits on ACME-4.