# Capture and edit issues

Create issues fast, write in Markdown, attach images, discuss in threads and recover things from the trash.

An issue starts as a title. Everything else can arrive later, and most of it edits in place.

## Before you start

- A workspace. See [Get started](/help/using/getting-started).
- Nothing else. Members, Admins and the Owner can all create and edit issues. [Who can do what](/help/using/views-and-settings#who-can-do-what).

## Steps

### Capture

1. Press **New issue**, or `c` from anywhere outside a text field.
2. Name the problem. Titles hold up to 300 characters; the good ones use about forty.
3. Optionally add a description and set **Status**, **Priority**, **Size**, **Assignee**, labels, a cycle or a project. Picking **Ready** also makes you tick **Refined and ready to start**. [Here's why](/help/using/status-refined-blocked).
4. Press **Create issue**, or `⌘/Ctrl+Enter`. Tick **Create another** when you're emptying your head.

Group headers in a list have their own **New issue in…** button, which fills in that group's value for you. **Sub-issue** on an open issue creates a child of it.

### Edit

- **Title:** click it, type, press Enter.
- **Description:** click it (an empty one reads "Describe the damage…") and write. Your draft is kept in the tab and saves when you leave the text, or press **Save changes**.
- **Everything else:** the properties beside the description, or right-click any row in a list.

### Write

The editor speaks Markdown and has a toolbar for people who'd rather not. `⌘/Ctrl+B`, `I`, `U`, `E` and `K` do bold, italic, underline, inline code and links. Behind **Aa** sit headings, lists, checklists, quotes, code blocks, tables, collapsible sections, dates and diagrams. Type `@` to link another issue. **Markdown** flips to the raw source, and **Copy Markdown** does what it says.

### Attach images

Paste, drop or browse. PNG, JPEG or WebP, up to 10 MiB each, up to 20 per description or comment. Images are private to the workspace: a link to one is useless to anybody who can't open the issue.

### Discuss

Comments sit under the issue. "Add your two cents…", then `⌘/Ctrl+Enter`. **Reply** starts a thread, emoji reactions save everybody a "+1", and **Resolve** closes a thread without deleting it. **Show the receipts** swaps the comments for the full activity history: who changed what, and when, including agents.

### Trash and restore

**Move to trash…** is in an issue's menu. Trash keeps the content and the relationships, hides the issue from ordinary lists and stops it blocking anything. **Restore issue**, from the **Trash** view, brings it back along with its blocking effect. Trash is not an archive: trashed issues become eligible for permanent removal after 30 days.

## What you should see

New issues land in **Backlog** as **Needs refinement** unless you chose otherwise. Edits show up straight away, and every one of them leaves a line in the activity history.

## If it goes sideways

- **"Save didn't land. Your draft did."** The network dropped. Your text is still in the editor. Press **Retry save**.
- **"This issue changed."** Someone, or something, edited it while you were typing. Review their version before reapplying yours. Hydrant won't pick a winner for you.
- **"Browser draft storage is unavailable."** Private windows and strict settings can do this. Drafts then live only in memory, so save before reloading.
- **"Image storage is full."** Remove images you don't need, or see plan limits under **Settings › General**.
- **Creation looked like it failed.** Press **Retry creation**. It's the same request, so you get one issue, not two.

Contact: bots@hydrant.dev