# Anatomy of an issue

Every property, plus sub-issues, comments, activity, and attachments.

Canonical: https://easerix.com/docs/tasks/issues

<Answer>
An issue is a title and description plus a rail of properties — Status,
Priority, Assignee, Project, Cycle, Due date, Estimate, and Labels — with
sub-issues, comments, an activity feed, and attachments underneath. Every
issue gets a permanent key like ENG-12, built from its team's key.
</Answer>

## Keys and where issues open

Issues are identified as `<TEAM KEY>-<number>`, like `ENG-12`. Clicking an issue anywhere opens a docked side panel for quick edits; **Open full page** takes you to the full view with the activity feed. `Esc` closes the panel.

## Properties

| Property | What it does |
|---|---|
| **Status** | The issue's place in the team workflow — new teams start with Backlog, Todo, In Progress, Done, and Canceled |
| **Priority** | Urgent, High, Medium, Low, or No priority |
| **Assignee** | One person owns the issue; unset shows as Unassigned |
| **Project** | The project it belongs to, if any |
| **Cycle** | The sprint it's scheduled into — see [Cycles](/tasks/cycles) |
| **Due date** | A calendar date; overdue issues get a red countdown chip |
| **Estimate** | Points: 1, 2, 3, 5, or 8 |
| **Labels** | Tags for filtering; manage them from the Labels card in Settings |

Moving an issue to a completed status timestamps it as done — that's what drives project and cycle progress bars.

## Title and description

Both edit in place: click, type, and it saves. The description supports **Markdown** — headings, lists, links, quotes, tables, code, and inline images. The composer has a formatting toolbar and a **Preview** tab, so you never have to write raw Markdown if you don't want to.

### Checklists in the description

Type `[] item` (or GitHub-style `- [ ] item`) on its own line and it renders as a real checkbox — `[x]` starts it checked. Click a checkbox to toggle it right from the rendered description; no need to open the editor. Checked items show struck through, and checklists nest with two-space indents.

```
Launch checklist:
[] draft the announcement
[x] book the demo environment
- [ ] final QA pass
```

The same Markdown works in **comments** (checkboxes there are display-only — edit the comment to change them).

## Sub-issues

Break work down without losing the thread.

1. On the issue, choose **Add sub-issue** and type a title — `Enter` creates it.
2. Sub-issues inherit the parent's project and cycle, and get their own keys.
3. The parent shows a `done/total` progress bar; each child links back to its parent with a breadcrumb chip.

## Comments and activity

- **Comments** support Markdown; you can edit or delete your own, and edited comments are marked `(edited)`.
- The **Activity** section on the full page merges comments with every property change — who moved it, reprioritized it, assigned it, and when.
- `⌘Enter` submits a comment.

## Attachments

Attachments ride along with descriptions and comments:

- Click **Attach** in the composer toolbar to pick images, or **paste** / **drag and drop** any file straight into the text.
- Files up to **15 MB** each. Images render as thumbnails on the issue; other files appear as named chips.

## Frequently asked questions

### Can an issue have more than one assignee?

No — one assignee per issue keeps ownership unambiguous. When several people share a piece of work, split it into sub-issues and assign each one; the parent tracks combined progress.