# Tasks

> Create and track tasks, break them into subtasks, and collaborate with comments, attachments and checklists.

> For the complete documentation index, see [llms.txt](https://helpdesk.orangescrum.com/llms.txt).

Source: https://helpdesk.orangescrum.com/guide/community/usage/tasks

---
Tasks are the unit of work. Each belongs to one project and carries a status,
priority, type, assignee and dates.

## Create a task

From inside a project, or from **Tasks** in the sidebar. The only required field
is a title — everything else can be filled in later.

| Field | Notes |
| --- | --- |
| **Title** | Required. Keep it an action: "Fix login redirect", not "Login" |
| **Description** | Rich text, supports attachments |
| **Assignee** | One person. Unassigned tasks are nobody's job |
| **Status** | `Open` or `Closed` |
| **Priority** | Low, medium, high, urgent |
| **Type** | Task, bug, and the other seeded types |
| **Due date** | Drives overdue filtering |
| **Milestone** | Optional grouping |

> **Statuses are fixed**
>
> The Community Edition ships `Open` and `Closed`. Custom task statuses and
> custom fields are commercial features.

## Subtasks

Break a large task into steps that need their own assignee or due date. Subtasks
are real tasks — they appear in lists and can be assigned independently.

Use a subtask when the piece needs to be owned or scheduled separately; use a
[checklist](#checklists) when it just needs ticking off.

> **Closing a parent does not close its subtasks**
>
> They stay open and keep showing up in filters. Close them first, or from the
> parent's subtask list.

## Checklists

Lightweight to-do items inside a task. No assignee, no due date — just a list
you tick.

Good for repeatable steps: a release checklist, a review checklist, a definition
of done.

## Comments and mentions

Discussion lives on the task, which keeps the reasoning next to the work rather
than in a chat log nobody can find later.

> **Tip**
>
> When you close a task, leave a comment saying what was actually done. Six
> months on, that comment is the only record of why the code looks the way it
> does.

## Attachments

Drop files onto a task or its description. They are stored on the server —
under the `orangescrum-app-files` volume in Docker — and appear in the project's
**Files** view.

Watch the size of that volume: attachments are the fastest-growing part of a
Community install, and they must be in your
[backups](https://helpdesk.orangescrum.com/guide/community/operate/backup-and-restore).

## Labels

Cross-cutting tags — `needs-design`, `blocked`, `customer-reported`. Unlike
status and priority, a task can carry several.

The **Label Customizer** plugin lets you rename labels to your team's own
vocabulary. See [Labels](https://helpdesk.orangescrum.com/guide/community/usage/labels).

## Milestones

Group tasks by delivery point — a release, a phase, a client deadline. A task
belongs to at most one milestone.

Milestones are the closest thing the Community Edition has to sprints. There is
no burndown, velocity or sprint report; those are
[Cloud features](https://helpdesk.orangescrum.com/guide/cloud/agile/overview).

## Views

- **List**: The default. Filter by status, priority, assignee and due date.

- **Kanban**: Under **More**. Columns by status; drag to move.

## Time

Log hours against a task manually — see
[Time entry](https://helpdesk.orangescrum.com/guide/community/usage/time-entry). There is no running timer in
this edition.

## What's not here

Task dependencies, custom fields, custom statuses, automation, recurring tasks
and import/export are all commercial features. Full list in
[What's included](https://helpdesk.orangescrum.com/guide/community/get-started/whats-included).

- [Next: time entry](https://helpdesk.orangescrum.com/guide/community/usage/time-entry): Logging and reviewing hours.