Skip to content

User guide

Hussein Jarrar edited this page Sep 12, 2026 · 2 revisions

How to use Radd: the work items, the views, the wiki, and every setting. Each page covers one part of the product.

If you are new

Read Start here first. It defines the words that the other pages use — work item, project, view, state, cycle, release — and it shows the first tasks you will do.

Then read The application window. It names every part of the screen, so the other pages can say "the rail" or "the pins bar" and you know where to look.

The work

Page Covers
Projects What a project owns, and what it shares with the server
Work items Epics, issues and subtasks; the item page; states and links
Views Saved queries with a display: boards, lists and planning
The card designer What a board card shows, and how to change it
Search and the query language Finding work, and the SLQ query language
Cycles and releases Time boxes, and the versions that ship the work
The roadmap Work on a timeline

Time, documents and messages

Page Covers
Time logging and the timesheet Estimates, worklogs, and the timesheet
The wiki Spaces, pages, versions and page links
Notifications and the inbox What Radd tells you, and how to change that
Reports and dashboards Charts, and the dashboards you build from them
Attachments Files on items and pages

Service desk and automation

Page Covers
The service desk Requesters, SLAs, canned responses and satisfaction
Intake forms and the portal How a request arrives
Automations Rules that act when something happens
AI features What the AI features do, and when they are turned off

Settings

Page Covers
Personal settings Your profile, appearance, tokens and sign-in security
Project settings The nine sections a project administrator controls
Instance settings Every server-wide section

What this guide does not cover

This guide is for a person who uses Radd. To extend Radd with a plugin, an editor extension or an automation node, read the Developer guide.

Pages


Mirrored from project.radd-hq.com on 2026-09-12. Documentation is written there; this copy is regenerated by scripts/publish_wiki.py and hand edits do not survive it.

Clone this wiki locally