# Task details

> The task page — comments, attachments, watchers, activity history and everything attached to a piece of work.

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

Source: https://helpdesk.orangescrum.com/guide/cloud/tasks/task-details

---
The task detail is where work actually happens. It gathers the description,
people, dates, subtasks, checklists, files, time and the full history in one
place.

## Layout

| Area | Holds |
| --- | --- |
| **Header** | Title, reference, status, priority |
| **Description** | Rich text, images, links, acceptance criteria |
| **Properties** | Assignee, dates, estimate, type, milestone, sprint, custom fields |
| **Subtasks** | Child tasks with their own owners |
| **Checklists** | Tick-off items inside the task |
| **Comments** | Discussion, with `@mentions` |
| **Attachments** | Files |
| **Time** | Logged hours against this task |
| **Activity** | Every change, with who and when |

## Comments and mentions

Discussion belongs on the task, not in chat. The difference shows up six months
later when someone asks why a decision was made — the task still has the
answer.

`@mention` someone to pull them in; they are notified and become a watcher.

- **Decide in comments**: If a decision was made in a call, write it here. Undocumented decisions get re-litigated.

- **Close with a summary**: A short "what was actually done" comment on close is the highest-value comment on most tasks.

## Watchers

Watchers get notified without being assigned. Useful for a lead who wants
visibility, or a stakeholder tracking one specific item.

> **Tip**
>
> Add a watcher instead of reassigning when someone only needs to *know*. Reassigning
> to signal interest is how tasks end up owned by people who are not doing them.

## Attachments

Drop files onto the task or embed them in the description. They count against
your workspace [storage](https://helpdesk.orangescrum.com/guide/cloud/plans/plans-and-limits).

For large files, link from Google Drive instead of attaching — see
[Google Workspace](https://helpdesk.orangescrum.com/guide/cloud/integrations/google-workspace).

## Time 

Start the timer or add hours manually from the task. Entries roll up into
[timesheets](https://helpdesk.orangescrum.com/guide/cloud/time/timesheets-and-approvals) and
[budget reporting](https://helpdesk.orangescrum.com/guide/cloud/time/budget-and-cost).

## Activity history

Every field change, status move, comment and time entry, with the person and
timestamp. This is the record that settles "when did this change?" and "who
moved it to done?".

On Premium, workspace-wide activity is also available in the
[audit trail](https://helpdesk.orangescrum.com/guide/cloud/admin/audit-trail).

## Linked work

- [Subtasks](https://helpdesk.orangescrum.com/guide/cloud/tasks/subtasks-and-dependencies): Break the work down; each child gets its own owner and date.

- [Dependencies](https://helpdesk.orangescrum.com/guide/cloud/tasks/subtasks-and-dependencies): "Blocks" and "blocked by" relationships that drive the Gantt.

- [Defects](https://helpdesk.orangescrum.com/guide/cloud/quality/defects): Link a defect to the task that introduced or fixes it.

- [Commits](https://helpdesk.orangescrum.com/guide/cloud/integrations/git-sync): Reference the task key in a commit message and it appears here.

## Keeping tasks readable

**A 60-comment task is a failure signal**

    It usually means the task is too big, or a decision is stuck. Split it, or
    escalate the decision — do not keep commenting.

**Update the description, don't bury changes in comments**

    If scope changes, edit the description. Nobody reads comment 23 to discover
    the acceptance criteria moved.

**Close tasks that are done**

    An open task that is finished distorts every report and every board.

- [Next: subtasks and dependencies](https://helpdesk.orangescrum.com/guide/cloud/tasks/subtasks-and-dependencies): Breaking work down and sequencing it.