Every deal, ticket, lead and account carries its own work. Three views of the same queue, on the same records as the rest of your CRM, with no second tool to keep in sync.
Unlimited tasks and unlimited users. MIT licensed, self-host it anywhere.
Columns you name, cards you drag, and a limit per column that the header actually counts against.
Four moves, and none of them need a second application open.
A title, notes, a due date, a priority, and the one record it belongs to. Custom fields your org defined show up on the form alongside the built-in ones.
Hand it to one person or several. Everyone named gets an email saying it is theirs, sent by a background worker that is tenant-aware.
It lands in their queue, which opens on unfinished work. It sits on the month calendar on its due date, and it surfaces on the dashboard once it is due today or late.
Tick it from the row itself. The tick is a save, not a local flourish: the row shows it is thinking, and takes whatever the server says back.
This page used to list both as headline features. Neither has ever existed for tasks, and knowing that up front is worth more than finding out in week two.
There is no repeat rule on a task: no daily, no weekly, no every-N-months. Completing one creates nothing after it. Recurring schedules exist in this product, on invoices, and an earlier version of this page borrowed that word for tasks. If a repeating checklist is central to your work, weigh this before you adopt.
No reminder emails, no mobile push, no daily digest. The one message tasks send is an email when a task is assigned to you. What replaces the nudge is visibility: the queue opens on unfinished work, overdue days are counted on the row, and the dashboard lists what is overdue or due today.
There is no multi-select on the task list, so no bulk reassign, bulk status change or bulk delete. There is also no CSV import or export for tasks in either direction. CSV import does exist here for contacts, leads and tickets, which is why this page used to claim it.
Logged hours, billable rates and the timesheet hang off a ticket, not a task. If you need hours against this work, do it on the ticket the task is pinned to. There is no timer on a task and no hours rollup by task.
Columns you name, cards you drag. Each column can carry a work-in-progress limit, and the header shows the count against it rather than a bare number, so a lane at 6 of 4 does not look like a lane at 2 of 5.
The list starts on unfinished work, because a to-do list that leads with history is not a to-do list. Completed tasks are one filter away, and the totals still count them.
Dated tasks sit on the day they are due. Seven columns on a laptop, and an agenda of only the days that carry work on a phone, from the same data, so the two can never disagree.
A task belongs to exactly one deal, ticket, lead or account, and the model enforces that rather than trusting the form. From the task you reach the record, and from the record you see its tasks.
Status, priority, assignee, due-date range, created range, tags, and the parent record. Custom fields are filterable too, so "billable and due this week" is a URL rather than a spreadsheet.
Admins, the person who created it and anyone it is assigned to can open it and change it. Deleting is narrower: admins and the creator only. Being handed a task is a reason to do it, not a reason to erase it.
The task model, the board and the permission rules are all in the open repository.
No to both, and they are the two things people most often assume. A task has no repeat rule, so completing one does not schedule the next, and nothing emails or pushes you before a due date. The only automatic message is the email sent when a task is assigned to you. What the product offers instead is that unfinished work is hard to miss: the queue opens on it, the row counts how many days late it is, the calendar shows the month ahead, and the dashboard surfaces what is overdue or due today.
It counts and it warns. A column with a limit shows the count against it, a lane past its limit says how far past, and the board header keeps a running count of how many columns are over. It does not block the drop: you can move a card into a full column and the server will accept it. That is deliberate on a shared board, where the useful behaviour is telling the team the lane is full rather than stopping one person mid-drag.
Anyone who is an org admin, created the task, or is assigned to it can open it, edit it and comment on it. Deleting is narrower: admins and the creator. The list applies exactly the same rule as the detail page, which matters more than it sounds. When the two rules drift apart you get a queue full of rows that answer 403 when you click them.
Everything the web list does and one thing it does not. On a phone you can browse and search the queue, filter by assignee, status and priority, switch to a calendar, create and edit a task, tick it done and delete it. Custom fields are on the mobile form and, today, not on the web one. The board is web-only.
Unlimited tasks, unlimited people, on your own database. Host it yourself, or let MicroPyramid run it.
