> ## Documentation Index
> Fetch the complete documentation index at: https://docs.timetracker.in/llms.txt
> Use this file to discover all available pages before exploring further.
# Task fields reference
> Every field on a TimeTracker task – what it means, what type it is, where you edit it, and which capability you need to change it.
This is the full reference for what a task carries. Use it when you are not sure what a field does or who is allowed to change it.
## Quick reference
| Field | Type | Where you edit it | Capability |
| ----------------- | -------------------------------------- | ------------------------------------------------ | --------------------- |
| Title | Text, 1–500 characters | Full task page header, or on create | `task.edit` |
| Description | Rich text | Detail pane → Description | `task.edit` |
| Project | One project | Detail pane → Details | `task.edit` |
| Section (stage) | One section of that project | Detail pane → Details, or drag | `task.edit` |
| Priority | No priority, Low, Medium, High, Urgent | Detail pane → Details | `task.edit` |
| Assignee | One member | Detail pane → Details | `task.edit` |
| Collaborators | Many members | Full page → More | `task.edit` |
| Start date | Date | Detail pane → Details | `task.edit` |
| Due date | Date | Detail pane → Details | `task.edit` |
| Tags | Many workspace tags | Full page → More | `task.edit` |
| Estimate | Hours | Detail pane → Estimate | `task.reviseEstimate` |
| Scope | One of five flags | Full page → Financials | `task.edit` |
| Budget cap | Hours or money | Detail pane → Budget cap | `budget.manage` |
| Visible to client | On / off | Full page → More | `task.edit` |
| Repeats | Daily, Weekly, Monthly | Full page → More | `task.edit` |
| Billable | On / off | Set on create; time entries carry their own flag | `task.edit` |
| Parent task | One task | Set when you create a subtask | `task.create` |
| Task number | Read-only text | Assigned automatically | – |
| Created | Read-only date and time | Assigned automatically | – |
## The fields in detail
### Title
The one required field. It must have at least one visible character after spaces are trimmed, and no more than **500 characters**. A blank title is refused everywhere, including when you clear the title input on the full task page – the field snaps back to the saved value.
### Description
A rich text body for context, requirements, links and acceptance criteria. Click the description area to edit it; it saves when you click away. Empty descriptions show a prompt instead of a blank box.
### Project
Which project the task belongs to, and therefore whose budget its hours consume. Changing it moves the task – including a new task number and its subtasks. Some moves are refused. See [/tasks/task-details](/tasks/task-details).
### Section
A task's stage **is** its section. Sections belong to the project and each carries a category:
| Category | Meaning |
| ----------- | ----------------------- |
| Not started | Work that has not begun |
| Active | Work in progress |
| Done | Finished work |
Moving a task into a Done section completes it. See [/projects/project-sections](/projects/project-sections).
### Priority
Five values, shown with an icon in the picker:
| Value | Label |
| -------- | ----------- |
| `none` | No priority |
| `low` | Low |
| `medium` | Medium |
| `high` | High |
| `urgent` | Urgent |
Tasks created from the project list or board start at **Medium**.
### Assignee
One person, and only a member of this workspace. The picker is searchable and shows avatars.
The Details picker has no "Unassigned" row. You change an assignee by choosing a different person. See [/tasks/assignees](/tasks/assignees).
If the task is not yours, an **Assign to me** link appears under the picker.
### Collaborators
Any number of extra people on the task, chosen from the workspace roster. Collaborators are people who care about the work; the assignee is the one person who owns it.
### Start date and due date
Two dates, both optional, both picked from the calendar.
They are **linked while they are equal**. Setting a start date carries the due date with it, so a one-day task never has to be dated twice. Setting a due date that differs from the start date breaks the link, permanently and visibly – after that, moving the start date leaves the deadline alone.
A new task with only a start date is due that same day.
A task is **overdue** when its due date has passed and it is not in a Done section. A task due today is not flagged until the day is over.
### Tags
Workspace-level labels drawn from a fixed 24-colour palette. Tags are shared across the whole workspace, so "Design" means the same thing on every project. See [/tasks/task-tags](/tasks/task-tags).
### Estimate
How long the work should take, in hours. A task carries two numbers:
| Number | Meaning |
| ----------------- | ---------------------------------------------- |
| Current estimate | What you now expect |
| Original estimate | The first estimate ever set. Never overwritten |
When the two differ, the panel shows "revised from Xh". Every revision is recorded with an optional note. See [/tasks/task-estimates](/tasks/task-estimates).
### Scope
A classification of how this task relates to what was sold. It is metadata, not a health signal.
| Value | Label |
| ----------------------- | --------------------- |
| `in_scope` | In scope |
| `additional_billable` | Additional billable |
| `needs_client_approval` | Needs client approval |
| `revision` | Revision |
| `internal` | Internal |
Anything other than **In scope** shows as scope impact in project financials, and appears as a badge on the board card.
### Budget cap
An optional cap on this one task, in hours or money, matching the project budget's unit. A cap is **informational**: it never reduces the project's available budget. Adding one needs `budget.manage` and the **Budgets** app. See [/budgets/task-level-caps](/budgets/task-level-caps).
### Visible to client
A switch that controls whether this task appears in the client portal. It is one of two doors – the project must also be shared with that client. See [/portal/what-clients-can-see](/portal/what-clients-can-see).
### Repeats
Turns the task into a recurring one. When on, you choose **Every N** and a cadence of **Daily**, **Weekly** or **Monthly**. The next occurrence is created when you complete the task, not ahead of time. See [/tasks/recurring-tasks](/tasks/recurring-tasks).
### Billable
Whether work on this task can appear on an invoice. Tasks created from the project list start as billable. Each time entry also carries its own billable flag, which is what invoicing reads. See [/concepts/billable-vs-non-billable](/concepts/billable-vs-non-billable).
### Parent task
Set when you create a subtask. Hierarchy is exactly one level deep – a subtask can never be a parent.
### Task number
A permanent, human-readable id in the form `-`, for example `WR-142`. Assigned when the task is created. See [/tasks/task-numbers](/tasks/task-numbers).
### Created
The date and time the task was created, shown at the bottom of **Details**. Read-only.
## Read-only figures on the Financials section
These are calculated, not stored on the task.
| Figure | What it is |
| -------------- | ------------------------------------------------------------------------------------- |
| Estimated | The current estimate, in hours |
| Tracked | Hours recorded against this task |
| Remaining | Estimated minus tracked, never below zero |
| Billable value | What the tracked billable hours are worth, in the project currency |
| Cost | What those hours cost you. Only shown if you hold `time.viewCost` or `rate.viewCost` |
| Budget | A chip reading **On budget**, **At risk** or **Over budget**, from the project rollup |
## Example
"Homepage wireframes" on Bluebird Coffee – **Website Redesign**:
| Field | Value |
| -------------- | ----------- |
| Task number | `WR-142` |
| Section | In progress |
| Priority | Medium |
| Assignee | Sarah Lin |
| Start date | Monday |
| Due date | Friday |
| Estimate | 6h |
| Tracked | 3h |
| Remaining | 3h |
| Billable value | \$300 |
| Cost | \$135 |
| Scope | In scope |
Sarah's billable rate is $100/hour and her cost rate is $45/hour, so 3 hours are worth $300 and cost $135 – a margin of \$165.
## Permissions
Nearly every field on this page is gated by `task.edit`, which Owner, Admin, Project Manager, Member and Contractor hold. The exceptions:
| Field | Extra requirement |
| ----------- | -------------------------------------------------------------------------------------------------------- |
| Estimate | `task.reviseEstimate` – Owner, Admin and Project Manager by default. A per-project override can widen it |
| Budget cap | `budget.manage` plus the Budgets app, which is a Pro feature |
| Cost figure | `time.viewCost` or `rate.viewCost` |
See [/tasks/task-permissions](/tasks/task-permissions).
## Common questions
There is not one. A task's status is the section it sits in, so your project's section names are your statuses.
The two dates had already been decoupled, because a due date was set that differed from the start date. That is deliberate – a deadline you pushed out stays where you put it.
Yes on the Tasks page, where the calendar offers a **No date** preset. Dragging a task into the **No date** bucket clears it too.
Time entries snapshot the rate that applies when the entry is saved. See [/concepts/rates-explained](/concepts/rates-explained).
## Related guides
Where each field lives on screen.
Current vs original, and revisions.
The 24-colour workspace palette.
Two numbers that are often confused.
Every term in one place.