Task management with boards and tickets
In Mono every piece of work is a ticket on a board. It has a number like ACME-121, the people working on it, a priority and a due date, and the comments and history stay on the ticket, so nobody has to ask where things stand.
Work gets lost between chat messages, spreadsheets and someone's memory.
When tasks live in a chat thread or a shared spreadsheet, nobody is sure who owns what, what changed or when it is due. The answers exist, but they are scattered, and finding them takes a meeting.
Mono gives each task one home: a ticket on a board. Who is assigned, what was said and every change made to it are on the ticket itself, and the board shows where all of them stand at a glance.
Looking for the contract side of the board? See project boards tied to client contracts.
Everything a task needs, in one ticket
Numbered tickets
Each task gets a short ticket number like ACME-121, made from its board's name, so your team can point to it in a message or a meeting and everyone finds the same thing.
Owners, priority and dates
Assign one or more people, set a priority, a start date and a due date, and add an estimate. Attach files or links the work depends on.
Comments and a full history
Discuss the work in the task's comments and @mention teammates to bring them in. The task's history records what changed on the ticket and who changed it.
Notifications that matter
People are notified when a task is assigned to them, when they are @mentioned, and when someone comments on a task they are assigned to, so they don't have to keep checking the board.
Boards that show the whole picture
Move tickets across kanban columns, or plan them into sprints on a scrum board. Search a board by title, ticket number or person, or filter it to one assignee.
Structure when you need it
Group tickets into epics and stories, break them into sub-tasks, and link related ones: one task blocks another, relates to it or duplicates it. Finished work can be archived and brought back.
One request, from message to done
A client emails asking for a new pricing section on their website. Instead of forwarding the email around, the account manager adds a ticket on the client's board: ACME-142, "Pricing section", assigned to a designer and a developer, high priority, due next Friday, with the email attached.
Both people are notified. The designer comments with a first draft and @mentions the developer, who moves the ticket to In Progress. When the client moves the deadline, the account manager updates the due date, and the new date and who changed it appear in the ticket's history.
On Monday the team lead opens the board, filters it to the developer, and sees ACME-142 next to everything else they own this week.
Anyone who opens ACME-142 sees who owns it, what was agreed and what changed, without asking.
How tasks and tickets work in Mono
Tasks, tickets and issues
Different tools call them tasks, tickets, cards or issues. In Mono they are the same thing: a task on a board, with a ticket number. The prefix comes from the board's name, so every task on a board called Acme is numbered ACME-1, ACME-2 and so on.
Four levels of work
Large pieces of work can be split into epics, stories, tasks and sub-tasks. You don't have to use all four: many teams use plain tasks on a kanban board and add epics only for bigger projects. Task types can be managed in the board settings.
Seeing your own work
The My Tasks list on the dashboard shows the tasks assigned to you, so you don't have to open each board to know what is yours. On a board, the assignee filter does the same for any team member.
Start managing tasks in three steps
Create a board
Choose kanban for continuous work or scrum for work planned in sprints.
Add your tickets
Add the work as tasks, assign people, and set priorities and due dates.
Work from the board
Move tickets across the columns, discuss them in comments, and let notifications do the chasing.
Part of one workspace
Each piece reads the same client, contract and task records, so delivery and billing never drift into separate systems.
Project boards tied to contracts
Kanban and scrum boards that belong to a client contract, so every task carries its scope, deadline and day allowance.
Time tracking
A timer and weekly timesheet where every hour is logged against a task — and so against a client contract.
Client management
Client records with contacts, notes, reminders and contracts — and an early warning before a contract expires.
Frequently asked questions
For your team's own work, yes. Every task is a numbered ticket with an owner, priority, comments and history. Mono is not a customer help desk: clients do not log in or open tickets themselves.
Yes. You can assign one or more people to a task, and each of them is notified (unless they assigned themselves).
Yes. Each task keeps a history of what changed and who changed it, next to its comments.
Boards, tasks and sprints are on every plan, including the free trial, which has limits on boards, tasks and sprints. See the pricing page for details.
Give every task one home.
Create a board and add your first tickets in minutes. The trial is free and needs no credit card.