Skip to main content
Tasks are the unit of work inside a project. A task carries a short ID such as ORG-145, a title, a rich description with attachments, a status, a type, a priority, one or more assignees, start and due dates, a checklist, dependencies on other tasks, comments and a change history. Built for the day to day work of a committee or staff team: who is doing what, by when, and what is blocking it. Replaces action-item spreadsheets and email chases. Tasks always belong to a project, so there is no standalone personal to-do list, but the My tasks page gathers everything assigned to you across projects.

Creating a task

Anyone with the Admin, Member or Contributor role on the project can create tasks; a Viewer cannot (see Roles). There are three ways in:
  • Quick add. Press C on the Tasks tab, or use Add task at the head of a group, and type a title. The new task starts with the values of the group you added it in. Type !high, @daniel, #bug or +review anywhere in the title to set the priority (!urgent, !high, !medium, !low, !none, or !1 to !4), the assignee, the type and the status; words that match nothing stay in the title. Enter adds the task, ⌘ Enter adds it and opens it.
  • Add task on the Board or Gantt tab, which adds a card in the column or opens the form.
  • Dropping files onto a project opens the form with those files attached.
Every task gets its ID on creation, built from the project’s task key and a number that counts up: ORG-1, ORG-2… Numbers are never reused, so a deleted task leaves a gap. The ID is searchable in the list. The list, board and Gantt only show the fields the project has switched on under Task options, so a project without priorities or due dates gets a simpler form.
Tasks used to have a fifth priority, Lowest. It has been merged into Low: tasks that were Lowest now read as Low.

The task panel

Click a task in the list, board or Gantt to open it in a panel beside the list, so you keep your place. The panel holds the title, the ID, a Copy link button, every field above, the checklist, the files and the comment thread. J and K (or the previous and next arrows) move to the neighbouring task while the panel is open, and Expand opens the task on a page of its own. Changes save as you make them, and the panel shows who created the task and when. Task detail page showing status, priority and type controls, two assignees with completion ticks, a three item checklist and a comment thread

Statuses and types

Both are defined per project under Settings → Workflow, so two projects can run entirely different workflows. A status has a name, a colour and a Mark as closed switch. Closed is what makes a task count as complete: it removes the task from open filters, from the daily digest and from reminder emails, and it satisfies any dependency on that task. A new project starts with Backlog, To do, In Progress, Review and Done, with Done marked as closed. Each status also draws a circle showing how far along it is, from dashed (no progress) to full. A type has a name and a colour only. It is a label for grouping and filtering. Deleting one asks whether its tasks move to another type or to No type.

Assignees

A task can have several assignees. On the board a task with several assignees has a card in each assignee’s swimlane when swimlanes are by assignee. Filters on assignee match a task if any of its assignees is picked, and the Overview workload counts the task for each of them. What a person may do to a task follows their role on the project. Admins and Members edit any task; a Contributor edits the tasks they created or are assigned to; a Viewer edits nothing. Admins delete any task, while Members and Contributors delete only tasks they created. On a project set to Only assigned, a Contributor cannot see other tasks at all. See Roles.

Dependencies

Blocked by lists tasks that must be finished first. Orgo enforces three rules when you add one:
  • the blocking task must be in the same project,
  • a task cannot block itself, and the chain cannot loop back on itself,
  • a dependency chain deeper than 100 levels is rejected.
While a blocking task is still open, moving the dependent task to a closed status is refused and the response names the tasks still in the way. Blocked tasks show a Blocked tag in the list and on the board, and the Gantt can draw the dependencies as arrows.

Comments and history

Comments sit at the bottom of the task. They take rich text, images and files, support threaded replies and emoji reactions. Viewers can read them, and can reply only when the project has Viewers can comment switched on. Posting a comment notifies the task assignees and the task creator in the app, and emails them (skipping whoever wrote the comment). On an archived project the comment is saved but nothing is sent. Status, priority, type, objective, due date and assignee changes are written to the history with who made it and when. Several changes to the same field by the same person within two minutes become one entry. Title, description and checklist edits are not logged.

Finding and organising tasks

The Tasks tab is the full list. Tasks show in groups, each with a header you can collapse. Deadline groupings also show the next few empty periods, so a task can be dropped into next week; Add period and Remove period adjust how many. The Overview tab’s counters are shortcuts into the same list: clicking overdue, due in 3 days, unassigned or no dates applies that filter.

Changing many tasks at once

Press X on a row (or use Select multiple) to tick tasks, then change their status, priority, assignee or type together, or delete them. Clear selection drops the ticks.

Manual order

Tasks have one order inside the project. Drag a row, or press Alt with ↑ or ↓, to change its rank; a task keeps its place relative to its neighbours in every grouping. The same order is used by the board columns.

Keyboard

? in the list shows the same table inside Orgo (Keyboard shortcuts). The Board tab is a kanban view with one column per status; dragging a card changes its status, and Swimlanes split the board by assignee, priority or type. The Gantt tab plots tasks on a timeline, and dragging a bar or its edges changes the dates. Both are described under Projects. The Board tab shows one column per status and the Gantt tab plots dated tasks on a timeline. Both are described in Projects.

My tasks

My tasks collects the tasks assigned to you across every active project, and is reached from the My tasks button on the Projects page or from View all on the dashboard card. Switch between Open and Completed (the last 90 days), group by Project, Due date, Priority or Month, filter by status, and mark a task done from its row. Archived projects and projects you have been removed from are left out. The dashboard My Tasks card shows your five open tasks that are due soonest, then by priority.

Emails about tasks

The digest groups your work into overdue, due today, due this week and high priority, and adds up to five tasks with no due date. If none of the first four groups has anything in it, no digest goes out that day. Archiving a project silences the first three emails for its tasks, and so does taking someone off the project: they stop hearing about tasks that stay assigned to them. The digest is the exception: it still lists tasks from archived projects.
Every task email can be switched off by the member with the Task toggle in their profile notification settings, and that switch stops all four emails above. The organisation default for new members is Email Notifications: Tasks under Settings → Modules → Emails & Notifications → Notification Preferences, and it ships set to Instant. The assigned, status changed and comment emails are not in the Email Templates catalogue, so their wording cannot be edited from Settings.
Orgo also has due soon and overdue task emails, but the job that sends them is not on the automatic schedule, so members do not receive them today. Use the daily digest, which lists the same overdue and upcoming work.

  • Projects - projects, access, goals and the project views
  • Issues - the separate issue tracker inside groups
  • Notifications - the notification switches and defaults
  • Emails - how system emails are built, sent and logged
  • Permissions - what organization admins and HR managers unlock