> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hiveku.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Project Tasks

> Track to-dos, bugs, and features per project with a kanban board

The Tasks tab in every Hiveku project is a lightweight kanban board for tracking work scoped to that specific site — bug reports, feature requests, polish items, follow-ups from client calls.

```
Project > Tasks
```

## Kanban Columns

Tasks flow through four columns:

1. **Backlog** — not started, waiting to be picked up
2. **In Progress** — actively being worked on
3. **Review** — done, waiting for QA or approval
4. **Done** — complete

## Creating a Task

<Steps>
  <Step title="Click + Create Task">
    Button at the top of the Tasks page.
  </Step>

  <Step title="Write a title">
    Short and actionable. *"Fix mobile hero overlap"* beats *"hero"*.
  </Step>

  <Step title="Pick a type">
    * **Bug** — something is broken
    * **Feature** — new capability
    * **Improvement** — enhancing what's there
  </Step>

  <Step title="Set priority">
    Low, medium, or high. High-priority tasks get highlighted in the board.
  </Step>

  <Step title="Pick a status">
    Defaults to **Backlog**. Change it if you're creating a task that's already in progress.
  </Step>

  <Step title="Assign it">
    Pick a teammate from the assignee dropdown. You must have teammates invited to the project — see [Invite Your Team](/how-tos/invite-team).
  </Step>

  <Step title="Set a due date (optional)">
    Shows on the task card. Tasks past their due date highlight red.
  </Step>

  <Step title="Create">
    Task appears in the chosen column.
  </Step>
</Steps>

## Moving Tasks Between Columns

Drag any card from one column to another. The task's status updates automatically.

<Tip>
  You can also click a task to open its detail view and change status from a dropdown there — useful on smaller screens where drag-and-drop is fiddly.
</Tip>

## Filters and Search

Above the board:

* **Filter by type** — bug, feature, improvement, or all
* **Filter by priority** — low, medium, high
* **Filter by assignee** — see only tasks for one person
* **Search** — type any part of the title

Filters stack. You can view *"all high-priority bugs assigned to Sam"* by layering three filters.

## Subtasks

For bigger items, break them down:

<Steps>
  <Step title="Open the parent task">
    Click a task card.
  </Step>

  <Step title="Scroll to Subtasks section">
    Below the description.
  </Step>

  <Step title="Click Add Subtask">
    Enter a title and optional assignee.
  </Step>

  <Step title="Check off subtasks as they complete">
    Each subtask can be independently marked done without closing the parent.
  </Step>
</Steps>

Subtasks roll up visually — the parent card shows `3/5 subtasks` completed.

## Task Detail View

Click any card to open the detail panel:

* Description (rich text, supports attachments)
* Comments (threaded conversation per task)
* Activity log (who changed what and when)
* Subtasks
* Linked items (discussions, commits, files)

## Stats Panel

Top of the Tasks page shows counts:

* **Total tasks**
* **Completed**
* **In progress**

Good for a quick project health check at a glance.

## Project Tasks vs. PM Projects

| Project Tasks                               | PM Projects                                                   |
| ------------------------------------------- | ------------------------------------------------------------- |
| Scoped to **this website project**          | Cross-project, account-wide                                   |
| Lives at **Project > Tasks**                | Lives at **top-nav > PM Projects**                            |
| Good for per-site to-dos, bug fixes, polish | Good for broader initiatives, non-site work, client retainers |

Tasks here stay with the project. For work that spans multiple sites or isn't tied to a specific website, use PM Projects.

## Verifying a Task Was Created

<Steps>
  <Step title="Check the column it's in">
    Your new task should appear in Backlog (or the column you picked).
  </Step>

  <Step title="Drag it to In Progress">
    The column count in the header should update.
  </Step>

  <Step title="Have the assignee confirm">
    If assigned to a teammate, they get a notification. Check they can see it.
  </Step>
</Steps>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Can't drag tasks between columns">
    Refresh the page — occasional browser extensions (especially drag-disabling ones) interfere. If it still doesn't work, try a different browser or use the status dropdown in the task detail view.
  </Accordion>

  <Accordion title="Assignee dropdown is empty">
    You haven't invited anyone to the project yet. Go to **Settings > Team** or see [Invite Your Team](/how-tos/invite-team). Once teammates accept, they show up as assignee options.
  </Accordion>

  <Accordion title="My task disappeared after saving">
    Check the filter bar at the top — an active filter may be hiding it. Click **Clear filters** to see everything. If it's still missing, check the activity log on the project (someone may have deleted it).
  </Accordion>

  <Accordion title="Subtasks won't nest under a parent">
    Subtasks can only be added from inside the parent task's detail view. If you created them as separate tasks, you'll need to delete and re-add them under a parent.
  </Accordion>

  <Accordion title="Stats panel counts are wrong">
    Stats count across all columns. If a number looks off, clear filters — the display respects active filters. A filtered view of "only bugs" will show only bug counts.
  </Accordion>
</AccordionGroup>

## What's Next?

<CardGroup cols={2}>
  <Card title="Use Project Discussions" icon="comments" href="/how-tos/project-discussions">
    Threaded team chat where tasks often start
  </Card>

  <Card title="Invite Your Team" icon="user-plus" href="/how-tos/invite-team">
    Add teammates so you can assign tasks
  </Card>
</CardGroup>