# Board, releases and documentation Updated: 2026-11-06 ## Components A project can be split into **components**: parts that ship separately but share the project's team, issue keys, workflow and permissions, for example *API*, *Driver App* and *Web Portal*. Anything that needs its own team, permissions, customer or workflow is a separate project. Projects without components work exactly as before. - **Setting them up:** project admins add components on the project page, tab *Components*. Each has a name, a short code shown on its coloured tile (`API`, `DA`), a description, a lead and a default assignee. *Archive* hides a component from the pickers, but it stays on its issues and releases. - **On an issue:** an issue belongs to at most one component (*Component* in the Details panel; empty = *Project-wide*). - A new issue without an assignee goes to the component's default assignee. - Changing the component removes a release of another component, and IT4S says so. - Moving the issue to another project keeps a component with the same code there. - Epics have no component of their own: an epic spans components through its issues. - Who may set it: the same people who may set the release (*Administration › Permissions*). - **Issue list and Board:** a *Component* filter (added with *+ Filter › Planning*), a *Component* column in the list, and on the Board *Group by: Component*. Bulk edit can set the component too. - **Release streams:** a release can belong to one component (*Component* on the release page); then it takes only issues of that component. On an issue, the *Release* picker shows the component's releases first, then the project-wide ones, and says how many releases of other components are hidden. - **Epics across components:** an epic whose issues have components shows *Progress by component* and lists its issues by component. *Create Issues for Components* makes one child issue per chosen component in one go, titled `[API] Title`. ## Board - One column per status across the projects of your scope. The toolbar works like the issue list's: **Views ▾** first, then the fixed chips Release, **Status**, Assignee and Type, the chips you added, **+ Filter** (or `F`) and *Reset all*. On the Board, *+ Filter* offers Priority, Epic, Tags, Component and Reporter. There is no filter panel. Chips that don't fit go behind *+ n filters*, and an active filter is blue with a **×** that resets it. - **Status** on the Board holds *Backlog* (show the Backlog column) and how long the **Done** column looks back: *Done: last 7 days* (default), 14 or 30 days, or all. - **View ▾** (right) holds *Group by*, *Expand all* / *Collapse all* and the switch **Show sub-tasks**; the search icon comes after it. - **Swimlanes:** **View ▾** › *Group by*: Epic, Story, Assignee, Type, Release or Component. Each lane can be collapsed, and IT4S remembers this per grouping; *Expand all* / *Collapse all* is in the same menu. - **Story** shows each story, task or bug with its sub-tasks in one lane, in board order. Sub-tasks appear here even when *Show sub-tasks* is off. Epics are in *No story*. - **Type** has one lane per type: Epic, Story, Task, Bug, Sub-task. - **Release** follows the order of the Releases list, with *No release* last. With several projects, the lane shows the project too (`WEB · 1.0`). - **Component** has one lane per component, with *Project-wide* last. - **Views:** *Views ▾* saves the board's filters, the status settings and the grouping under a name, and brings them back with one click. The board has its own views, separate from the issue list's; see [Issues](https://it4s.at/en/help/guide/issues/). - Drag a card to change its status and order, or use *Move to…*; *Undo* in the message takes it back. Cards move between columns within their lane. Each column shows the count and the sum of the estimates. - A **pencil dot** next to the type means someone else has unsaved changes on that issue right now; hover to see who. ## Releases - A release (fix version) belongs to a project: name, status (Unreleased, Released, Archived), start and release date, description, and optionally a component. - **Project filter:** the *Project* chip on the Releases page shows the releases of some projects only, without changing the project scope in the top bar. It offers the projects of your scope that have releases, and IT4S remembers your choice. If you narrow the scope so that none of the chosen projects is in it, the chip goes back to *All*. - **By component:** when the projects of your scope have components, the Releases page shows one row per release stream, with its lead and a timeline. - The timeline shows the last released version, then the upcoming ones by date; the next one is marked as current, with its progress. - Project admins can *Plan next release* right there. - *View: List* switches to the table. ### The release page A release opens for reading: - The heading is the release's name (*Release 2.4*); the line under it names the project and the last change. - **Overview** (first tab, read-only): progress as a bar by status with the counts, **blocked issues** and what they wait for (an open issue of the project that *blocks* them), the **unfinished issues** with their assignee, the **dates**, and the **release notes** (*Write →* / *Edit →* opens their tab). - **Publish…** (project admins, while the release is unreleased) asks first, then sets it to *Released*, with today's date unless one is set. If issues are still open, IT4S asks where to move them; cancelling that keeps the release unreleased. - Then the tabs **General** (where you edit the release) · **Release Notes** (Markdown; *Generate from Issues* drafts notes from the done issues) · **Issues** (with Done 12 / 15) · **Documentation**. The bar *Cancel · Save and Close · Save* shows only while something is unsaved. - A **new** release shows *General* and *Issues*; the notes and documentation come after the first save. - A release of an inactive project shows a banner and is read-only. - **Generate with AI** (when an admin has switched AI on): Claude writes release notes for your customers. - **Content:** a short summary, *New features*, *Improvements*, *Bug fixes* and, if issues are still open, *Known issues / not included*, with the issue keys as links. - **What it uses:** only what customers may see (titles, descriptions, types, statuses, epics, tags), never internal notes, technical plans, prompts or comments. - **Language:** choose it next to the button (*English* or *Deutsch*); it starts with your UI language. - **While it writes:** the text appears in the editor; *Cancel* stops and brings back your text. - **Existing notes:** if the editor already has notes, choose *Replace* or *Add at the End*. - **Saving:** nothing is saved until you click Save, and *Undo* in the message restores the previous text. - **Releasing** with the status pill works too, and with open issues it asks where to move them. ### Plan a release: the Issues tab Project admins pick the issues of a release on its **Issues** tab, on *Add Release* and on every unreleased release. Released and archived releases, and other users, see the list of its issues. - **Available** (left) lists the open stories, tasks and bugs that could go in, grouped by epic (*No epic* last). Sub-tasks are not listed: they always follow their parent. - **Source:** *Open, no release* (default), *Backlog only*, or *In other unreleased releases* (the row says `in 1.25`; moving it takes it out of that release). - **Filters:** Type, Epic, Priority, Assignee, Tags and a search field; *Views* saves them like on the issue list. - A release of a component offers only that component's issues. - **In 1.24** (right) lists the release's issues by rank. Both sides show *Select all* and the sum of the estimates. - **Moving:** tick issues and press **→** or **←**, drag them across (a ticked row takes the other ticked ones along), or double-click a row. Moved rows are marked *New* or *Taken out*. - **Saving:** nothing changes until you click **Save**. The tab gets a dot, and the footer says what will happen, for example *4 issues will go into 1.24 · 1 issue will be taken out of 1.24*. *Cancel* forgets the moves. Saving moves each issue with its open sub-tasks, and the issue's history shows the new release. - If an issue cannot go in (it belongs to another component, or to a release that is already released), nothing is saved and the message names the issue. **Suggest issues with AI** (when an admin has switched AI on; on a saved release): 1. Choose the **focus**: *Balanced*, *Features* (stories users notice) or *Technical & bugs*. 2. Check the **capacity**: IT4S fills in the working days up to the release date (like `7d`); you can also enter hours (`40h`) or story points (`20 pts`). 3. Click **Suggest Issues**. Claude reads the open issues (title, start of the description, type, priority, status, estimate, epic, tags, age and what blocks them) and what is already in the release, and proposes the ones that fit, best first, each with a short reason in your language. 4. **Add** a proposal, **Dismiss** it, or **Add All**. Proposals are also marked *AI* in the Available list. The AI only proposes: nothing goes into the release until you add proposals and click Save. ## Documentation - *Work › Documentation*: pages per project, nested as subpages, with refs like `WEB-DOC-3`. Filter by release; the project comes from the scope. - Arrange pages by drag and drop or the row menu (Move Up/Down, Indent, Outdent). - Pages are Markdown with images and files. Issue keys (`WEB-42`) show as chips with title and status; the issue's *Sub-tasks & Links* tab lists the pages that mention it. Toolbar *Link Issue* inserts a key. - When you edit a page, the main area has only the title and the editor. **Release** and **Visibility** are in the *Details* panel on the right (collapsible, like on issues), together with the page's ref, version and who created and changed it. - Each page has comments and a history; delete moves the page and its subpages to the trash with Undo. - Projects show their pages in the *Documentation* tab; releases in theirs. - Pages of an inactive project show a banner and can't be edited. - **Who else is here:** like on issues, a page and its edit page show the pictures of the others who have it open; a pencil means unsaved changes in their editor, and a hint warns you when you both edit. ### Internal and public pages - Every page is **Internal** (only the team) or **Public** (the project's customers can read it too). Choose it under *Visibility* in the Details panel when you edit the page. - New pages start with the project's *Default Documentation Visibility* (project settings); unless an admin changed it, that is **Internal**. - A public page is only shown to customers when **every page above it is public too**. The tree marks public pages with *Public*; *Public · hidden* means a page above is internal, so customers don't see it yet. - Customers see the public pages in the tree, in search and on their issues, but not the comments or the history of a page, and they cannot edit.