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

# Issues & Tasks

> Track tasks, assign work, and manage projects within groups — with backlog and kanban views

Issues is a lightweight project management tool built into every group. Create tasks, assign them to members, track progress with statuses, and visualize work on a kanban board. No separate tool needed.

***

## Do I need Issues?

| You want to...                       | Issues?                                       |
| ------------------------------------ | --------------------------------------------- |
| Track action items from meetings     | Yes                                           |
| Manage a project with assigned tasks | Yes                                           |
| Plan event logistics with a team     | Yes                                           |
| Log bugs or problems to fix          | Yes                                           |
| Manage a content calendar            | Yes                                           |
| Handle member support requests       | Use [Help Desk](/platform/help-desk) instead  |
| Track personal to-dos                | Not ideal — Issues is for group collaboration |

***

## Enabling Issues for a group

Issues are enabled per group, not globally:

1. Go to the group's settings
2. Enable **Issues/Tasks**
3. Configure which features are active

| Setting             | Default | What it controls                              |
| ------------------- | ------- | --------------------------------------------- |
| **Priority levels** | On      | High, Medium, Low priority on issues          |
| **Due dates**       | Off     | Target completion dates                       |
| **Issue types**     | On      | Categorize as Task, Bug, Feature, etc.        |
| **Status tracking** | On      | Workflow columns (To Do → In Progress → Done) |

***

## Creating an issue

Go to any group's **Issues** tab → click **Add Issue**:

| Field           | Required | Description                                     |
| --------------- | -------- | ----------------------------------------------- |
| **Subject**     | Yes      | Brief title — "Book venue for annual meeting"   |
| **Description** | No       | Details, requirements, links, context           |
| **Type**        | No       | Task, Bug, Feature, Research (if types enabled) |
| **Assignee**    | No       | Who's responsible                               |
| **Priority**    | No       | High, Medium, or Low                            |
| **Due date**    | No       | When it should be done (if dates enabled)       |
| **Attachments** | No       | Screenshots, documents, reference files         |

***

## View modes

### Backlog view

A flat list of all issues. Sort by date, priority, status, or assignee. Filter and search to find what you need. Good for reviewing everything at once.

### Kanban view

A visual board with columns for each status. Drag issues between columns to update their status. See progress at a glance. Good for daily standups and active project tracking.

***

## Customizing the workflow

### Statuses

Default statuses:

| Status          | Meaning                        |
| --------------- | ------------------------------ |
| **To Do**       | Not started                    |
| **In Progress** | Someone's working on it        |
| **In Review**   | Waiting for review or approval |
| **Done**        | Complete                       |

Create custom statuses to match your workflow: go to the group settings → **Issue Statuses** → add, rename, reorder, or color-code statuses.

### Issue types

Default types:

| Type         | Use for                    |
| ------------ | -------------------------- |
| **Task**     | General work items         |
| **Bug**      | Problems to fix            |
| **Feature**  | New things to build or add |
| **Research** | Investigation or analysis  |

Create custom types in group settings → **Issue Types**. You can set default assignees per type — e.g., all "Budget" issues auto-assign to the treasurer.

***

## Working with issues

### Filtering

Filter by status, assignee, type, priority, due date, author, or creation date. Combine filters to focus on what matters — e.g., "High priority, assigned to me, In Progress."

### Notifications

Members get notified when:

* They're assigned to an issue
* An issue they're watching changes status
* Someone comments on their issue
* A due date is approaching

***

## Common scenarios

<AccordionGroup>
  <Accordion title="We use Issues for meeting action items — any tips?">
    Create issues during the meeting with clear subjects and assignees. Set due dates for accountability. Use a "Meeting Actions" type so you can filter by it later. Review open items at the start of the next meeting.
  </Accordion>

  <Accordion title="The kanban board has too many columns">
    Keep it simple — 3 to 5 statuses is ideal. "To Do", "In Progress", and "Done" works for most teams. Add "In Review" if you have an approval step. More columns means more friction.
  </Accordion>

  <Accordion title="Can issues be shared across groups?">
    No — issues belong to one group. If multiple groups need to track work together, create a shared private group for the project and use issues there.
  </Accordion>

  <Accordion title="What's the difference between Issues and Help Desk?">
    Issues are for internal team work — tasks, projects, action items among group members. Help Desk is for support — members submit tickets, a support team responds. Different workflows, different audiences.
  </Accordion>

  <Accordion title="Nobody is updating their issue statuses">
    Make it part of the routine. Review the board in meetings. Keep the workflow simple. If people find it burdensome, you probably have too many statuses or required fields.
  </Accordion>
</AccordionGroup>

***

## Related

* [Groups](/platform/groups) — Where issues live
* [Help Desk](/platform/help-desk) — Member support tickets
* [Files](/platform/files) — Attach documents to issues