Tasks are the unit of work on a Boardssey project board. This page covers creating them, breaking them into subtasks, assigning them, and moving them through the columns of your board.

What this page helps you do

Add a task and fill in its details.
Break a task into subtasks for tracking sub-steps.
Assign tasks to teammates and set due dates.
Move tasks across columns as work progresses.

Add a task

On a project board, click Add task at the top of any column (or the + on a column header). A small task creator appears.

The minimum is a title. Type it and press Enter to create the task in that column. You can edit everything else later.

For more detail upfront, click into the task to open the full editor.

Task fields

Open a task and you'll see:

Title: short summary of the work.
Description: detail, links, context. Supports rich text.
Status: which column the task is in. Change it from the editor or by dragging the card.
Assignee(s): who's responsible. Multiple assignees are allowed.
Due date: when this should be done. Shows on Calendar and All Tasks.
Priority: Low, Medium, High, or Critical.
Tags: free-form labels for cross-cutting categorization (art, playtest-blocker, p1).
Attachments: files relevant to the task.
Subtasks: see below.
Comments: see Task comments.

Subtasks

For tasks that have multiple steps, break them into subtasks instead of making the description long.

In the task editor, click Add subtask. Type the subtask title and press Enter. Subtasks appear as a checklist under the parent task.

What you can do with subtasks:

Check them off as you complete them. The parent task shows a progress indicator (e.g. "3/7 done").
Promote a subtask to a full task if it grows beyond a checklist item. Open the subtask's menu and pick Promote to task. It becomes a standalone task (and disappears from the parent's checklist).
Reorder by dragging.
Assign each subtask to a different person if needed.

Use subtasks for short, well-defined steps within one piece of work. Use separate tasks when each step has its own due date, owner, or non-trivial description.

Assigning a task

In the task editor, click the Assignee field and pick from the team members list. The person sees the task in their All Tasks view filtered to "Assigned to me" and (if their notifications allow) gets a notification.

Multiple assignees are allowed when more than one person is responsible.

To unassign, remove the person from the field. Anyone with edit access to the project can assign and unassign.

Setting a due date

Click the Due date field and pick a date. The task now appears on the Calendar view (see Calendar) and shows up in All Tasks sorted by due date.

Overdue tasks turn red on the board and are flagged in Project Stats.

Moving tasks across columns

Two ways:

Drag the card from one column to another on the board. Drop it where you want it within the new column.
Edit the status in the task editor and pick a new column.

Both work; the drag-drop is faster for routine moves, the editor is better when you're already inside a task.

Bulk operations

Select multiple tasks (Shift-click or Cmd/Ctrl-click on cards) to bulk:

Move to another column.
Assign or unassign.
Tag or un-tag.
Delete.

Useful for cleaning up a backlog or moving a sprint's worth of completed tasks to Done at once.

Tips & common questions

Do tasks belong to a specific game? A task belongs to a project. If the project is linked to a game, the task inherits that game association. Standalone projects have tasks that aren't attached to any game.

Can a task be on more than one board? No, each task is on exactly one project board. To represent cross-project dependencies, link tasks via descriptions and tags, or use external project management for cross-functional initiatives.

What's the difference between a tag and a column? A column is a status (where in the workflow). A tag is a category (art-needed, blocked-on-X). Tasks live in one column at a time but can have many tags.

Can I set recurring tasks? Not today. We're tracking recurring tasks on the roadmap.

Can I lock a task so others don't edit it? There's no per-task lock. Project-level access is what controls who can edit. See Sharing access on a game if you need narrower scoping.

Where do completed tasks go? They stay in whichever "Done" column you've defined. Some teams archive periodically by moving Done tasks to an Archive column or deleting in bulk.