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 quietly fall out of date.
Sections
- Getting started: signing up, your company, users, 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, with every field, operator and function.
- Automation: rules, events, conditions, actions, checks 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 user's profile.
- Rights and access: roles in a company and in a project, and borrowed administrator rights.
- Two-factor authentication: a second factor at sign-in, backup codes, and the company's own rule about it.
- 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.
- Service accounts: accounts for integrations, tokens, OAuth clients and token rights.
- API: the address, signing in with a token, errors, limits and the method reference.
How to read these pages
The terminology matches the interface: rule, event, condition, action, draft, publication, check, company, issue. The unit of work is an issue here, no matter what the tool you are coming from called it.
Every heading has a permanent link: hover over the heading and click the hash sign. Page addresses and anchors do not change after publication, so you can link to them from your internal policies and guides.