# Issues

Updated: 2026-11-06

## Types and statuses

| Type | Icon | Use | Parent |
|---|---|---|---|
| Epic | purple tile, lightning bolt | a large feature that groups work | – |
| Story | green tile, bookmark | something users notice | an epic (optional) |
| Task | blue tile, check mark | technical work | an epic (optional) |
| Bug | red tile, target ring | a defect | an epic (optional) |
| Sub-task | teal tile, branch arrow | a step of a story, task or bug | required |

The type icons follow the colours and shapes known from other trackers, so you can tell types apart at a glance; the shape alone also tells them apart. Hover an icon for the type's name. Notification emails show the same icon next to the issue.

Every project has the same workflow: **Backlog → To Do → In Progress → In Review → Done**, plus **Won't Do**. Any status can move to any other (unless an admin limited this for your role). Priorities: Highest, High, Medium, Low, Lowest. Issues have keys like `WEB-42`; moving an issue to another project gives it a new key, and the old one keeps working.

**Parents close by themselves:** when the last open child of an issue is set to Done or Won't Do, the parent follows: **Done** if at least one child is Done, **Won't Do** if all are. This goes up the tree, so closing the last sub-task can close its story and then the epic. The change is made in the name of the person who closed the child (if their role may not make that move, the parent stays open), and the parent's Activity says *closed it with its last open child issue WEB-42*. Reopening a child does not reopen the parent; deleting a child does not close it.

## Project scope

The **switcher on the left of the top bar** chooses which projects you are looking at: one, several, or **All projects**. It applies to every work page: My Work, Issues, Board, Releases, Documentation, Worklogs, Time Report and Estimate Report. These pages have no Project filter of their own.

- **Choosing projects:** click the switcher, or press `P`. Search, pick from *Recent*, tick projects, or use *Only this* on a row. *All projects* resets the choice. Inactive projects are folded at the bottom.
- **Project groups:** when your workspace has project groups, they are listed under *Project groups* with the number of their projects (e.g. *Fleet · 4 projects*). Ticking a group adds all its projects to the scope, unticking removes them; a half-ticked box means some of them are chosen. *Only this* on a group shows exactly its projects. The scope still lists the projects, so you can untick single ones afterwards.
- **Saved for you:** the scope is remembered for your account, so it follows you to other devices.
- **Sharing:** work pages keep the scope in the address. A link someone sends you opens with their projects, and a message offers *Use my scope* to switch back.
- **Pages without a scope:** on the issue page, Projects, Administration and Settings the switcher is greyed out with *Not filtered by project on this page*.
- **Documentation** shows one project of the scope. When the scope has several projects, a chip on the page picks one.

## My Work

Your start page. The **dashboard card** on top shows:

- **Counts** in one row: open issues, issues due in 7 days, issues waiting for your review, and new mentions (and your agents' issues, if you have agents).
- **With AI switched on,** a short daily summary with next steps, in your language, as a full-width card under the counts. AI text is violet with ✦.
- ***What's new*** since your last visit and ***Needs to be done*** (your open issues by urgency, with the reason) side by side, five items each, then *Show more*.
- **The last 7 days** as a slim strip: a small pair of bars per day (opened, closed) and the totals as the legend. A bar or a total opens those issues.

Below the card is the list of your open issues. Both follow the project scope. The list has the same toolbar as the issue list (Release, **Status** with default *Open*, Type and *+ Filter*); it has no Assignee chip, because it lists your issues, and it always shows sub-tasks.

**Waiting for your review** counts issues that are In Review and either assigned to you or **reported by you**. When a customer reports a bug and the assignee sets it to In Review, the customer is asked to check the result. These issues:

- appear in *Needs to be done* with the reason *In review*
- show in *What's new* as *set it to In Review: ready for your review*, with a *Review* chip
- are named in the AI summary

The tile opens the issue list filtered to these issues.

## Issue list (Issues)

The **toolbar** is the one place to filter; there is no filter panel. From left to right:

- **Views ▾:** your saved views (see *Views* below).
- **Fixed chips:** Release · Status · Assignee · Type.
- **Chips you added** with **+ Filter** (or press `F` anywhere on the page). The menu has a search field *Find filter …* and the other filters in groups: *Planning* (Priority, Epic, Tags, Component), *People* (Reporter), *Time* (Due, Created, Updated, Resolved), *More* (Drafts, Templates). Filters already shown are greyed out. The chip you pick opens its options at once; **×** on an added chip removes it again. IT4S remembers which chips you added.
- **Date chips** start with presets:
  - **Due:** *Overdue* (with the number of open issues past their due date), *Today*, *This week*, *Next 7 days*, *No due date*, *Range …*.
  - **Created, Updated, Resolved:** *Today*, *Last 7 days*, *Last 30 days*, *Range …*.
  - Only *Range …* shows the two date fields. A preset stays a preset: a view saved with *Due: Today* always means the current day.
- **Reset all** appears after *+ Filter* while a filter is active.
- Chips that don't fit the width go behind **+ n filters**, which opens them; the toolbar never wraps.
- An **active filter** is blue with its value in bold and a small **×** that resets just that filter. *+ n filters* turns blue when one of its hidden filters is active.
- **View: List ▾** (right), a chip of the same size as the filters: *List* or *Tree*, *Group by* (in the tree, with several projects), *Expand all* / *Collapse all*, the switch **Show sub-tasks**, *Columns…* and *Density*. It is highlighted while open.
- **Export** as CSV with the round download icon next to it.

More about the list:

- **Status:** *Open* (default), *Done* or single statuses; the same chip and options are on My Work and the Board.
- **Assignee:** *Me*, ***Me (assignee or reporter)*** (the issues you are the assignee or the reporter of), *Unassigned*, *All people*, *All agents*, then *My agents* and the people.
- **Drafts** (*+ Filter › More*): *Drafts: With my draft* shows the issues you have unsaved text on (see *Drafts* below), also in My Work, where it lists them whoever they are assigned to. Such issues carry a small *Draft* badge next to the title in both lists.
- **Release and Epic follow the project scope.** This also applies on the Board, the Time Report and the Estimate Report.
  - With projects chosen, you only get their releases and epics.
  - With *All projects*, releases are grouped by project, so two releases called "1.0" can be told apart.
  - A release or epic that no longer fits the scope is removed from the filter, and IT4S says so (*Release filter reset*).
  - On the Board, releases that were released since are removed too.
- **Templates** (*+ Filter › More*): *Only templates* or *Without templates*.
- **List or tree view:** the tree shows epics with their stories and sub-tasks.
- Sort by any column, choose columns, and IT4S remembers your filters; *Reset all* keeps the project scope.
- Select rows for **bulk edit** (status, priority, assignee, release, tags) or delete.
- **Add Issue** (top right) picks the type; a template issue can prefill a new one.
- **One search:** the issue list searches with the quick search next to the title; the toolbar has no second search. To jump anywhere in IT4S, use *Search or jump to* in the top bar (`/`, see [Getting started](https://it4s.at/en/help/guide/getting-started/)).

### Quick search

The **search field between the title and *Add Issue*** finds issues fast in the projects of the scope switcher. No other filter applies: status, assignee, views and the rest are ignored for it.

- **What it searches:** key, title, description and comments. Every word is found **inside** other text and regardless of case (`log` finds *Login*). Customers only search the comments they can see.
- **Operators:** a space or `AND` / `&&` / `&` means both words; `OR` / `||` either word; `!word` or `NOT word` without it; `"export pdf"` exactly this text; brackets group, for example `(rls OR tenant) && !staging`. `UND`, `ODER` and `NICHT` work too. AND binds before OR. The **?** in the empty field shows the syntax. A query with an open bracket or a trailing operator is searched as its plain words.
- **Results while you type:** a box below the field lists up to 8 matches with key, type, title and status. Matched words are marked; a match in the description or a comment shows the passage, labelled *Description* or *Comment*. The number of all matches is at the bottom.
- **Open an issue:** click it, or pick it with ↑ ↓ and press Enter.
- **Matches in the list:** *Show all in the list*, Enter without a picked result, Esc or a click elsewhere closes the box, and the list below shows exactly the matches (as a flat list, sub-tasks included). A blue note says so; × in the field or on the note clears the search and brings the list back with its filters.
- **Layout:** the field is a line that takes the free width of the header row and turns blue while you type in it; the box of results is as wide as the field. On a phone it gets its own row under the title.
- All terms are text: `!done` leaves out issues that **contain** "done", not issues in status Done. For status, use the Status chip without the quick search.

### Views

**Views ▾** at the start of the toolbar keeps filter settings you use often:

- **Save:** *Save Current Filters as View…* stores everything you set on the page under a name, for example *My open bugs*: the filter chips (also the ones added with *+ Filter*, and date presets as presets), *List* or *Tree*, the grouping and the sort. Tick *Also choose the projects …* to store the current project scope with it; otherwise the view works with whatever projects are chosen. Saving under an existing name replaces that view.
- **Apply:** pick a view from the menu, and the page switches to its settings at once. While nothing differs from it, the button shows its name; change a filter, and the button goes back to *Views*.
- **Rename** and **delete** with the pencil and the bin next to a view (they appear on hover); *Undo* in the message brings a deleted view back.
- Views are yours and follow you to other devices. The issue list, My Work and the Board each have their own views.

## The issue page

The page is made for reading first:

- **Header:** the issue's **title** is the heading. The line under it says type, key, project and *updated … by …*; the breadcrumb ends with the key (*Issues / WEB-80 / WEB-87*). Under it are **pills** for status and priority.
- **Save only when needed:** the bar *Cancel · Save and Close · Save* at the bottom appears only while something is unsaved, with *● Unsaved changes*.
- **Details** on the right: type, project, epic or parent, then assignee, release, due date and tags. **More fields** below holds reporter, component and the estimates; it stays open or closed as you left it, and opens by itself when a field in it has an error. An **ⓘ** after a field's name explains it when you point at it.
- **Status and priority save at once:** pick a value in a pill, and it is stored right away, without *Save*. The message *Status changed to Done* offers *Undo*.
  - Other changes you have not saved yet (title, description, details) stay as they are, and *Save* stores them afterwards as usual.
  - If someone else changed the same field in the meantime, their value stays and the pill shows it, with a message naming who changed it.
  - On a **new** issue the pills are part of the form and are saved with *Create*.
- **Tabs:** Overview · Description · Sub-tasks & Links · Comments · Attachments · Time Tracking · **⋯**. The page opens on **Overview** (see below). *Time Tracking* shows the time logged so far, like *Time Tracking (4d 7h)*.
  - The **⋯** menu holds Technical Plan, Prompts, Designs, Activity and Internal. Customers see only Activity there.
  - Entries show their count, or a dot when they have content; the ⋯ itself gets a dot when one of them does.
  - The tab you open from the menu stays visible next to ⋯ until you pick another one. Links like `…/issues/WEB-42?tab=designs` open it directly.
- **Description and comments** are Markdown: headings, lists, task lists (`- [ ]`), code, tables. Paste or drop images and files. Type `@` to mention someone (see *Watchers and @mentions* below); mentioned people get an email, also when mentioned in the description.
- **Images and files on a new issue:** you can paste, drop or insert them right away, before the first save, and the *Attachments* tab is there too. Customers can add screenshots and documents when they report a bug. The files belong to the issue once you click *Create*. If you cancel, they are removed after a day.
- **Comments** are *internal* by default; *public* comments are what customers see.
  - **Visibility** is a pill like status and priority, next to *Add Comment* and when editing a comment: *Visibility: Internal* with an amber lock or *Public* with a blue globe; the menu explains both. Every posted comment shows the same icon and word, so internal and public comments can be told apart at a glance. Customers don't choose; their comments are always public.
  - They are listed **newest first**; the *Sort* chip switches to *Oldest first*. Your choice is remembered and also applies to comments on documentation pages.
  - *Add a Comment* follows the order: on top for newest first, at the bottom for oldest first. Your new comment appears right next to it, briefly highlighted.
  - `Ctrl+Enter` adds the comment.
- **Comment categories:** a comment can say what kind of contribution it is: **Decision**, **Question**, **Answer**, **Blocker**, **Action Item** or **Info**, each with its own icon and colour.
  - **When writing:** the *Category* pill next to *Visibility* (*None* by default).
  - **Later:** *Category ▾* on the comment changes or removes it. You can do this on your own comments; members and admins on every comment. The history records the change.
  - **Questions** are *Open* until answered. *Answer* on a question starts a reply that answers it: a bar above the editor names the question, the category is *Answer*, and posting it marks the question *Answered* (× makes it a normal comment again). *Mark as Answered* closes a question without a reply; *Open Again* reopens it. An answered question has *Show Answer*.
  - **Show:** the pill above the comments filters them: *All comments*, *Open questions (2)*, or one category with its count.
- **Sub-tasks & Links:** add sub-tasks, link issues (*blocks*, *relates to*, *duplicates*), and **Code**: pull requests, branches and commits with their state (Open, Merged, …) and CI checks. With the GitHub integration, they appear by themselves when a PR or commit names the issue key.
- **Activity** (in the ⋯ menu): every change with who did it and how ("Chris via Claude Code", "… via GitHub").
- **Delete** moves an issue (with its sub-tasks) to the trash; *Undo* or *Restore* brings it back.
- If someone else changes the issue while you edit, IT4S tells you who, instead of overwriting their change.
- **Inactive projects:** an issue of an inactive project shows a banner *Project … is inactive – read only* (admins can activate it there), and its fields show their values read-only.

### Overview

The issue page opens on **Overview**: a read-only, compact picture of where the issue stands. Each section links to its full tab (*Open Description →*, *All comments →*, *Time Tracking →*, *History →*); nothing can be edited here. Sections without content shrink to one line, such as *No links or sub-tasks · Add →*.

- **General / For me** (top right): *General* is the same for everyone. *For me* adds what needs your attention and picks the comments that matter to you. It opens by itself for the assignee, the reporter and watchers when something needs them; otherwise *General* opens, with *Nothing needs your attention* when you are involved. Your last choice is remembered for all issues.
- **Needs your attention** (For me): a comment that mentions you and that you have not answered yet (*Reply*); a **question** that mentions you stays here until it is marked answered, even after you replied; the description changed by someone else since your last visit (*View Diff* shows the lines removed and added); and, when you are the assignee, a missing due date while the issue is in an unreleased release (*Set Date* opens the Details).
- **AI summary** (when AI is on): *Generate Summary* / *Regenerate Summary*. *For me* writes it for you and ends with **Open for you**; each view keeps its own summary, your *For me* one is yours alone. Labels show what it was built from (description version, comments, linked issues, time tracking). After new comments or description edits it is marked *Outdated · 3 changes since*; it is not rewritten by itself. It lists decisions, open questions and blockers from the comment categories.
- **Key facts:** type, assignee, reporter, epic or parent, story points, time logged against the estimate as a bar, tags.
- **Description**, condensed: the first paragraph, the first three checklist items (read-only), then *+ 2 more items* and the section headings, and the word count.
- **Comments:** at most three, each labelled with why it is shown: *Mentions you* and *Unread* (For me), *Open question*, *Blocker*, *Decision*, *Reporter, unanswered* (the reporter's latest comment while nobody answered it), and always the newest (*Latest*). The number of open questions shows next to the comment count. A long comment fades out at the bottom with **Show more**, which opens it right there (*Show less* folds it again).
- **Progress** (logged, also by you; remaining; sub-tasks done), **Links & sub-tasks** with their status, and **Recent activity** (the last five entries; those since your last visit have a filled dot).
- **Your last visit:** IT4S notes when you had an issue open for a few seconds (not in lists or on the board). Visits less than 15 minutes apart count as one, so a reload keeps the markers until you come back later. Only you see your visits.

### Watchers and @mentions

Mentioning someone and pulling them into an issue takes one step.

- **Suggestions:** type `@` in the description, a comment or a documentation page, and IT4S suggests the people with access to the project, agents included (with their AI badge). Keep typing to narrow the list by name or email; pick with ↑ ↓ and Enter (or Tab), or click; Esc closes the list. The mention goes into the text as `@mara.berger`, and the person gets the usual mention email.
- **In the text:** mentions show in the link colour. A click opens a short **profile card** with picture, name and email (*AI agent* for agents).
- **Add to watchers:** on an issue, the card offers *Add to watchers*; if the person already watches, it says *Watching*.
- **Watch ▾** in the header lists the watchers. Members, admins and customers also find *Add someone* there to put another person of the project on the watch list. Viewers can watch issues themselves but not add others.
- The person you add is **not notified**; the history says *Ada added Mara Berger as watcher*. Only the watchers themselves can stop watching; nobody removes someone else.

### Who else is here

- Next to *Watch* you see the pictures of the other people who have the issue open right now (up to three, then *+2*). Hover for *Mara Berger is viewing*.
- A **pencil** on a picture means that person has **unsaved changes** (*is editing*). If you start changing the issue too, a hint says *Mara Berger is editing this issue too. Save soon or talk to them first.* Nothing is blocked; if they save first, IT4S tells you before you overwrite their change.
- Someone appears within a few seconds and disappears when they leave the page or close the tab (at the latest after about a minute). A tab in the background does not count. Customers are not shown and do not see others.

### Drafts

What you type is kept as a **draft** until you save it, so a reload, a crashed browser, an expired session or a lost connection does not lose it. This works in the issue description, technical plan and prompt, the title and description of a new issue, new and edited comments (also on documentation pages), the title and content of documentation pages, release notes, and a project's description and internal note.

- **While you type:** a second after you stop, the draft is kept on this device and on the server. The line under the editor starts with *Draft saved 15:47*. Without a connection it says *Offline: draft kept on this device*, a banner says your text is kept, and the draft is sent once you are back online.
- **When you come back** to a field with a draft (after a reload, on another computer), a note above it says *Unsaved draft from 29.10.2026, 15:47* with:
  - **Restore:** puts the draft into the field. It is still not saved; *Save* (or *Add Comment*) saves it.
  - **Show differences:** your draft next to the saved text. If someone saved a different text after your draft started, the note is a warning and the comparison also shows the text from when you started, so you can see what they changed before you overwrite it.
  - **Discard:** asks once (*Discard draft?*) and removes the draft.
- **When a draft ends:** *Save*, *Add Comment*, *Cancel* and *Discard* remove it. Signing out removes the drafts on that device; the server keeps them for your next sign-in. Drafts nobody touched for 30 days are removed.
- **Private:** only you see your drafts. They are not in the history and change nothing for others; the saved content changes only when you save.
- **Finding them:** issues you have unsaved text on carry a *Draft* badge in My Work and the issue list; *+ Filter › Drafts: With my draft* lists them.
- A new documentation page keeps no draft before its first save.