These pages describe what is built and running. Every statement here is checked against the product's code, and the QQL reference tables are generated from that code — when the product changes, the page cannot silently stay behind.
Sections
- Getting started: signing up, your company, people, roles, the first project, and what happens after the trial.
- CSV import: moving issues from any tracker through one file, validated before anything is written.
- QQL reference: the query language — every field, operator and function.
- Automation: rules, events, conditions, actions, dry runs and outbound calls.
- Workflows: statuses, transitions, revisions, and going back to an earlier version.
- Organization chart: the reporting tree, built from a profile field.
- Profile fields: your company's own fields on a person's profile.
- Rights and access: roles in a company and in a project, and borrowed administrator rights.
- Issue security: levels on a single issue, overlaying project permissions.
- The audit trail: what is recorded on every change, where to read it and how to search it.
How to read these pages
The terminology matches the interface: rule, event, condition, action, draft, publication, check. What other products call a ticket is an issue here.
Every heading has a permanent link — hover over it and click the hash sign. Page addresses and anchors do not change after publication, so they are safe to reference from your internal playbooks.