Features
Everything it does.
Grouped by the job at hand.
Plan the work, hand the routine parts to your tools, listen to the people using what you shipped, and measure whether any of it landed.
32 capabilities · five groups · shipped, not planned
1.0Shape the work before it starts
Workspace, space, folder, list, then a list view and a board over the same filtered set.
-
FIG 1.1
Two views, one filtered set
List and board render the same filtered set, and the filter bar sits above both, so switching view never loses your filters. Neither view waits for the whole list before it shows you anything.
- Filters survive the switch
- Counts stay accurate
- Nothing to wait for
To do7Retry the export path on 5xxWidget accent contrastIn progress4Materialize notification intentsPublic roadmap votingIn review2Speed up the orders list -
10ktasks, same speed
Lists that open at any size
A list with ten thousand tasks opens as fast as an empty one, and stays that way as the year fills it up.
-
Subtasks, five levels deep
Deep enough for real decomposition, capped so nobody builds a tree the team cannot read.
-
FIG 1.2
Dates you can drag
Month, week and day views, drag-to-reschedule, and week swimlanes for a whole team at once. Roadmap milestones sit on the same grid.
Google Calendar beside your tasksMon10Tue11Wed12Thu13Fri14Sat15Sun16Retry the export pathWidget accent contrastBeta cut Orders listCustomer emailsRoadmap voting -
Workspace → space → folder → list
A hierarchy that matches how teams already divide work, instead of one flat bucket of tasks.
-
Custom fields where they belong
Defined on a space or a single list, with editors for text, number, date, select, multi-select and checkbox.
-
A roadmap above the spaces
Initiatives across quarters with milestones, health, and progress rolled up from the spaces beneath.
-
Whiteboards that draw the diagram
Realtime boards in the same workspace as the tasks. Describe a block diagram and it is drawn as editable shapes, matched to 1,285 official architecture icons. On every plan.
AI whiteboards and diagrams- AWS
- Azure
- Kubernetes
2.0Talk where the work is
A chat in every space, direct messages and small groups, in the same workspace as the tasks they turn into.
-
1 clickfrom message to task
Any message becomes a task
Choose Create task on a message and it is filed into the list you used last in that conversation, with a link back to the message it came from.
- Remembers your list
- Links both ways
- Works in DMs too
-
A chat in every space
Each space has its own conversation, so a project is discussed where it lives. Direct messages and groups of up to eight cover the rest, with threads to keep side discussions out of the way.
-
Task cards that stay live
Mention a task and it shows as a card. When its status changes, the card in the chat changes too.
-
Decisions you can find again
Mark a message as a decision and it joins the conversation’s decisions log. Pin what people keep asking about.
-
Catch up in one read
Missed more than six messages? A summary is waiting at the top, with the tasks it suggests, ready to create.
-
Email only when it is still unread
Mentions and direct messages reach your Inbox. An email follows only if they are still unread an hour later.
3.0Let your tools do the updating
43 MCP tools, a scoped REST API, and GitHub links that track the branches, commits and pull requests.
-
43MCP tools, live
Your assistant, on the same rails
Anything your assistant does goes through the same permission checks and validation as a click in the app, and leaves the same activity trail. A token can only reach the workspaces you name and do the things you tick.
- 24 scopes
- 120 requests/minute
- revocable, expiring
-
FIG 3.1
GitHub work, attached to the task
Issue, branch and pull request links with commit and PR tracking, and a diff you can read without leaving the task.
Linked work
#482 Export retries drop the last batch Openbranchfeat/export-retry6 commits#35 Harden the retry window +214−38 Mergeda8f4339harden retry backoff on 502 and 5042f1c0b7add jitter so retries do not synchronise
-
One pipeline, three doors
A click, a tool call and an API request take the same path. There is no faster, looser way in.
-
A REST API with the same model
Scoped tokens, the authorization pipeline MCP uses, and a monthly request quota per tenant.
-
Actions attributed to a person
Reads use one business token; writes use each member’s own, so GitHub shows who actually did it.
-
Realtime, not refresh
Boards, lists, task drawers and the inbox update as your team works.
-
Two people, one task, nothing lost
When two people edit the same task at once, the second one is told and offered the newer version, instead of quietly overwriting the first.
4.0Turn a bug report into a task
One script tag collects the report, triage turns it into work, and email tells the reporter it shipped.
-
FIG 4.1
A queue, not another inbox
Submissions land in one triage view. Approve to create a task, merge into the task that already exists, or reject with a reason and an image. The reporter stays linked either way.
- approve
- merge
- reject with a reason
Needs triage12 Approved5 Published9PD-7QK2M4XD Export stops at 500 rows BUGApprove → new task Merge into #482 RejectPD-J3V8R1PC Bulk edit from the board FEATURE 24 ▲PD-M2X9T4KD Timezone on the calendar chip BUG merged -
One script tag, no account
The widget embeds in your own product and takes bugs and feature requests from people who never sign in. It carries your colours, and runs anonymous or identified.
-
Publish the ones you will do
Feature requests become a voteable public board, in the widget and on a standalone page.
How the public roadmap works -
The reporter hears back twice
Acknowledged on submit, emailed again when it ships, including merged duplicates.
-
A reference they can quote
Every submission gets a short code that appears in the subject line of every email about it, so the thread stays findable in the reporter’s own inbox.
- PD-7QK2M4XD
5.0Cycle time you can defend
Dashboards and per-person views computed from recorded status transitions, with counts and chart bars that open their tasks.
-
Dashboards that click through
Throughput, cycle time and workload widgets, where a count or a chart bar opens the tasks it counted rather than leaving you to reconstruct them.
Dashboards with drill-down -
FIG 5.1
Every status change, timestamped
The transition is written the moment it happens, so time-in-status is read back rather than remembered. Cycle time ends up a measurement instead of a number estimated at the end of the sprint.
Status transitions
Backlog1d 4hIn progress2d 1hIn review10hDoneCycle time
2d 11h in progress → done · median 2.4d -
Person analytics, section by section
Per-person views split into sections, with drilldowns that page as you scroll.
-
Workspace stats at a glance
Totals, completed and overdue, plus the split by status and priority, counted server-side.
-
Who actually has capacity
Team availability read from the work already assigned, rather than from a spreadsheet of guesses.
- AR · 6 open
- MK · 3 open
- SD · 9 open
-
Reports you can hand over
Seven period reports, from timesheets to delivery and estimate accuracy. Pick the columns, compare with the previous period, and export to CSV, Excel or PDF.
See the reports- CSV
- Excel
See it on your own backlog.
Free for up to 5 people, and the first month on Basic or Pro is free. Connect an MCP client in one command, drop the widget into your product, watch the first report become a task.