Compare
Keep the flexibility for notes; give delivery a dedicated issue model.
For teams running bugs and sprints in a general workspace. Notion Projects is flexible and does a great deal: databases, sprints, docs, AI and MCP. Nothing Left is narrower on purpose: an issue tracker in which keys, links, sprint state, time logs, burndown and project runbooks are built in.
Issues should behave like issues, even when the team also writes docs.
A general workspace can be shaped into an issue tracker, and it can work well. The trade-off is who keeps the shape. In Notion Projects the team builds its own task model from databases and keeps it consistent. In Nothing Left the issue model comes built in. You cannot redesign it, and you do not have to maintain it.
In Notion Projects, you assemble it
- Tasks are items in a database. The team picks their properties and views, and each view can be a board, a timeline, a calendar or a chart. Views, filters and sorts
- An ID property with a prefix gives tasks keys, and sub-items and dependencies are switched on per database. Unique ID
- The sprints setup adds current, next and last sprints and a Complete sprint button. Sprints
- Docs, wikis, Notion AI and Notion MCP sit in the same workspace as the tasks. Notion Projects
In Nothing Left, it is already there
- Every issue has a key such as ACME-12, a type, a priority, a status, story points, a sprint, an estimate and spent time. You do not have to set any of this up.
- Links read from both ends, and a depends-on loop is refused before it is saved.
- Sprints are planned, active, then completed. The burndown is recorded every night, so editing an issue later does not rewrite the chart.
- Each project has its own private knowledge base. An issue key in an article links to the issue, and the issue links back.
Notion details are taken from its own product and help pages, linked above. A Notion workspace can be set up in many different ways, so we describe what it offers rather than draw one.
Notion Projects and Nothing Left, row by row.
What each one builds in, with a source for every cell. Limited means the capability is there with a narrower scope, and the note says how. Filter by group, or read the whole table.
Notion Projects column last verified against its own pages on . Product names are trademarks of their owners.
Show
| Capability | Nothing Left | Notion Projects |
|---|---|---|
| Planning | ||
| Issue keys | YesEvery issue gets its project key and the next number, such as ACME-12, on creation. The number never changes and the key is the issue’s address in the app, the API and the agent tools.Issues manual: keys | YesAdd an ID property to a database and every item is numbered from 1. With a prefix, an item also opens at an address such as TASK-123.Notion: unique ID |
| Links, subtasks and dependencies | YesRelates to, depends on, duplicates and subtask of, each read from both ends. A depends-on loop is refused, and a key typed in any text becomes a link.Issues manual: links | YesSub-items and dependencies are switched on per database. Dependencies can shift dates on a timeline when one item moves.Notion: sub-items and dependencies |
| Sprint state | YesA sprint is planned, active, then completed, with one active sprint per project. Finishing it asks where unfinished issues go, and resolved ones stay with the sprint.Agile manual | YesThe sprints setup adds a sprint board and a sprints database with current, next and last sprints. Complete sprint moves them along and asks where incomplete tasks go.Notion: sprints |
| Configurable databases and views | LimitedIssues have a fixed shape. Admins set statuses, priorities, types and custom fields, and saved views filter the list, backlog and board. You do not design your own databases or layouts.Custom fields manual | YesAny database with properties you choose, shown as a table, board, timeline, calendar, list, gallery or chart, with nested AND/OR filters.Notion: views, filters and sorts |
| Permissions | YesFive built-in roles: two for the organisation, three per project. There are no custom roles and no per-page sharing.Permissions | YesAccess levels per page, such as Full access, Can edit and Can edit content. Teamspaces have their own members, and guests are invited by email.Notion: sharing and permissions |
| Delivery | ||
| Time logs against an estimate | YesLog a date, a duration and a work type. Spent time shows against the estimate and includes subtasks, and timesheets and a time report add the logs up.Issues manual: time tracking | LimitedThere is no time-log property among the documented property types. Teams record time in number, date or formula properties they add.Notion: database properties |
| Sprint burndown | YesRemaining work per day against an ideal line, recorded nightly. Scope added after the start is its own line.Reports manual: burndown | LimitedThe sprints guide describes no burndown. A line chart view with Cumulative on can plot a count or sum over time from one database.Notion: charts |
| Reports scoped by a query | YesNine reports, each scoped by a search query, a saved view or projects. Every bar opens the issues it counts, and each report exports to CSV.Reports manual | YesChart views draw bar, line and donut charts from a database, using the view’s filters. Drilling into a chart opens the items as a table.Notion: charts |
| Docs and wiki | LimitedEach project has a private knowledge base of markdown articles, readable only by its members. An issue key in an article links both ways. It is not a company-wide wiki and cannot publish to the web.Knowledge base manual | YesPages and wikis across the whole workspace, with page owners and verified pages. Pages can also be published to the web.Notion: wikis and verified pages |
| Agents | ||
| Agent access over MCP | YesAn MCP server over HTTP. The agent acts as the person who connected it, within their role and the token’s scopes and projects.MCP manual | YesNotion MCP lets assistants such as Claude, ChatGPT and Cursor read and write pages and databases with the connecting person’s permissions.Notion: Notion MCP |
| Built-in AI assistant | NoThere is no assistant inside the app. You bring your own agent and connect it over MCP.MCP manual | YesNotion AI drafts and reformats pages, answers from the workspace and connected apps, builds databases from a description and takes meeting notes.Notion: Notion AI |
| Hosting and pricing | ||
| Hosting | 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 | NoA cloud service. Its plans page lists no self-hosted edition.Notion: plans |
| Plan | YesNo subscription for any team size during beta, and the first 20 members stay free permanently. 5 GB of storage per organisation, unless you connect your own bucket.Limits and billing | YesA free plan and paid plans per member. Full Notion AI comes with Business and Enterprise, and Free and Plus get a limited trial. Prices are on its pricing page.Notion: 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.
One bug, from its sprint to its write-up.
ACME-12 as it stands on 13 Oct 2026, in a fictional project three weeks in. Each step below opens the same piece of work from a different angle. Pick a step to see that screen.
1 / 4The bug, fixed by Alex Lee
Invite link blank after it expires
- Status
- Fixedresolved 8 Oct 2026, 4:40pm
- Reporter
- Casey Kim
- Assignee
- Alex Lee
- Sprint
- Sprint 08
- Story points
- 3
- Severity
- Critical
- Spent time
- 1h 45m of 2h
Subtask of
ACME-3Make invitations clearer
Depends on 1
ACME-4Invite expiry setting per org, resolved
Referenced by 1
Invitation links and expiryDecision record
2 / 4Its sprint, on 13 Oct 2026
Make invitations clearer
4 Oct – 17 Oct 2026 · 4 days left · 21 of 34 points resolved
Open3
Invite email subject names the org, assigned to Casey Kim
Resend invite from the members list, assigned to Alex Lee and Sam Ortiz
Upload stalls at 100% on slow links, unassigned
In Progress2
Swimlane header overlaps count, assigned to Casey Kim
Invite landing shows the inviter, assigned to Alex Lee
Fixed6
Invite link blank after it expires, assigned to Alex Lee
Project-scoped invite links, assigned to Jordan
Accept invite while signed in, assigned to Alex Lee
3 more
Fixed is a done status, so ACME-12 counts as resolved for the sprint and its burndown. When the sprint is finished, you choose where its unfinished issues go, and the resolved ones stay with it.
3 / 4The burndown, read live on 13 Oct 2026
Project ACMESprint Sprint 08Measure Story points
- Remaining
- Ideal
- Added after the start
Daily figures
| Date | Remaining | Ideal | Scope | Added | Done |
|---|---|---|---|---|---|
| 4 Oct | 31 | 31 | 31 | 0 | 0 |
| 5 Oct | 34 | 27.9 | 34 | +3 | 0 |
| 6 Oct | 31 | 24.8 | 34 | +3 | 3 |
| 7 Oct | 25 | 21.7 | 34 | +3 | 9 |
| 8 Oct | 22 | 18.6 | 34 | +3 | 12 |
| 9 Oct | 14 | 15.5 | 34 | +3 | 20 |
| 10 Oct | 14 | 15.5 | 34 | +3 | 20 |
| 11 Oct | 14 | 15.5 | 34 | +3 | 20 |
| 12 Oct | 13 | 12.4 | 34 | +3 | 21 |
| 13 Oct | 13 | 9.3 | 34 | +3 | 21 |
The same report can be scoped by a search query or a saved view, and an agent asking for it through run_report gets this table.
4 / 4The write-up, in ACME’s knowledge base
Decision record · Published to project members · Alex Lee, 2 Oct 2026
Invitation links and expiry
Invitation links expire after seven days. An expired link must say so and offer a new one; a blank page is a bug.
First seen in ACME-12, now resolved, so its key is struck through.
- Page
- /projects/ACME/articles/invitation-links-and-expiry
- For agents
- article://ACME/invitation-links-and-expiry
Only ACME’s members can read it. There is no public page and no anonymous access. Runbooks and post-incident write-ups live in the same tree.
Hand-drawn product views with fictional data. More on sprints and boards and the project knowledge base.
Which one fits, or both.
These are different tools. Notion is a workspace in which a team can build project tracking; Nothing Left is project tracking with a small knowledge base attached. Choose by where most of your team’s day goes.
Choose Notion if…
- Most of your team’s work is writing: specs, meeting notes, a company wiki, pages several teams share. Wikis
- You want to design your own databases, properties and views for each team, not adopt a fixed issue model. Views
- You want an AI assistant built into the workspace that drafts pages and answers from your connected apps. Notion AI
- You publish pages to the web, or rely on database automations that send webhooks, emails or Slack messages. Automations
Choose Nothing Left if…
- Bugs and sprints are the daily work, and you want keys, links, sprint state, burndown and time logs on every issue without building them.
- You want reports scoped by the same query language as search, with each figure opening the issues it counts.
- Your project runbooks and decision records should sit next to the issues they name and stay private to the project.
- You want your own agent to work through documented MCP tools, or you want to self-host the AGPL-3.0 build.
The third option
Use both: issues here, shared docs in Notion.
Run bugs, sprints, time and reports in Nothing Left, and keep the company wiki, plans and cross-team pages in Notion. Write the project’s own runbooks and decision records in its knowledge base if you want an issue to list them under Referenced by.
There is no built integration between the two. A link from a Notion page to an issue, or from an issue to a Notion page, is an ordinary link, and nothing is kept in sync.
What you would pay, next to Notion.
Notion is selected, starting from its lowest paid plan. Replace that with what your team pays and see what the beta takes off the bill. Notion's prices are on its own pricing page, linked below, and 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 Notion'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 Notion'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.
Moving tasks across from Notion.
There is no native Notion importer, and nothing is moved in one click. There are two routes, and both expect you to check the result.
- CSV, the dependable route. Notion exports a database as CSV, with a markdown file for each page.Notion’s export guideNothing Left’s generic CSV import maps its columns and dry-runs every row before anything is created.
- An agent, guided by you. Connect the same agent to Notion MCP and to Nothing Left. It reads your open tasks and creates the projects, tags and issues through documented tools, as you and within your role.Connecting an agent
Review before you rely on it
- Access: the agent sees what your Notion connection can see, and nothing more
- Mapping: which Notion properties become which fields, statuses and types
- Duplicates: tasks that already exist as issues
- Attachments and images inside task pages
- People: Notion members matched to Nothing Left members
- History: Notion’s edit history does not come across; each issue’s history starts when it is created
Questions from teams on Notion.
About sprints, docs, agents, moving tasks and cost. Short answers here, sources linked.
Does Notion Projects have sprints, AI and MCP?
Yes. Notion’s sprints setup has current, next and last sprints with a Complete sprint button, Notion AI is built in, and Notion MCP lets an assistant read and write a workspace. This page does not claim otherwise. The difference is that an issue tracker builds keys, links, sprint state, burndown and time logs into every issue, where a general workspace builds them from databases the team sets up. Notion’s sprint guide
Can Nothing Left replace our Notion wiki?
No, and it does not try to. Each project has a private knowledge base for runbooks, decision records and write-ups, readable only by that project’s members. It has no company-wide wiki, no public pages and no free-form databases. Keep the wiki where it is. Knowledge base manual
Can we use both?
Yes. A team can keep broad shared docs in Notion and run bugs and sprints in Nothing Left. There is no built integration between the two: link from one to the other by address, and keep project runbooks next to the issues they name if you want the issue to point back to them.
How do we move tasks across from Notion?
There is no native Notion importer. Notion can export a database as CSV, and Nothing Left’s generic CSV import takes it, with a dry run first. You can also connect one agent to both through their MCP servers and have it carry tasks across, with you reviewing the field mapping, duplicates, attachments and people before anything is created. Notion’s export guide
Does Nothing Left have a built-in AI assistant?
No. It has an MCP server, so the agent you already use reads and changes issues, sprints, reports and articles as you, within your role and the scopes of the token you give it. Connecting an agent
What does it cost next to Notion?
Nothing during beta, for a team of any size; the first 20 members stay free permanently once billing exists. Notion’s own prices are on its pricing page, and the calculator above links there rather than copying them. Pricing
Give the next bug an issue, and keep writing where you write.
Join the beta, create a project and file the bug you are working on now. Plan it into a sprint, log time on it, and write the runbook beside it when it is fixed.