Glossary
This glossary defines the terms used across Orbit, Forge, Pulse, Folio and Lumen. Each entry links to the page that explains it. Orbit is the work tracking product and also the name of the whole platform.
| Term | Meaning |
|---|---|
| Agent | A custom assistant you define in Lumen, with a name, instructions, the tools it may use and the projects it covers. See Agents. |
| API token | A secret that lets a script call the API as you. It can be read-only, can be limited to some projects, and is shown once. See API authentication. |
| Board | A Scrum or Kanban view that shows the work of a saved filter as cards in columns. Moving a card runs the workflow transition. See Boards, backlog and sprints. |
| Component | A part of a project, with an optional lead and a rule for who gets new work. See Project settings. |
| Confirm card | A change that Lumen proposes as a card. Nothing happens until you press Run, and your browser makes the change with your own permissions. See Actions with confirmation cards. |
| Custom field | A typed field that administrators add to work items, such as text, number, date, select or user. See Custom fields, screens and schemes. |
| Environment | A place where code is deployed. Forge keeps an immutable history of its deployments. See Environments, deployments and releases. |
| Form | A set of questions whose answers create a work item. See Forms that create work. |
| Goal | An outcome that you link work items and projects to. Its progress is derived from the linked work. See Goals. |
| Incident | A Pulse record, declared from an alert or by hand, with a severity, a commander and a timeline. See Incidents and postmortems. |
| Ingest key | A secret that belongs to one Pulse project and lets a service send telemetry. It is shown once and can be revoked. See Send your first logs. |
| JQL | The JQL-style query language that searches work items. See Search and JQL reference. |
| Manifest | A JSON description, in the format orbit-lumen-manifest/v1, that a product publishes so that Lumen can use it. See Add a product to Lumen with a manifest. |
| Merge request | A request to merge one branch into another in a Forge repository, with review, approvals and a pipeline. See Merge requests and approvals. |
| Monitor | A Pulse query that is evaluated every minute and keeps a state for each group it watches: OK, WARN, ALERT or NO_DATA. See Monitors and alerts. |
| Organization | The company account behind a site. It owns the site. Plans will give it one storage quota shared by all products, which is planned. See Organizations, sites and roles. |
| Page | A document in a Folio space, with an owner and a review interval. See Your first space and page. |
| Pipeline | A run of the jobs that a repository defines in its .gitlab-ci.yml. See Your first pipeline. |
| Plan | A cross-project timeline with dependencies, team capacity and scenarios. See Plans, teams and capacity. |
| Project | The unit of membership for every product. Work, code, telemetry and knowledge belong to a project, and its roles decide who may read or change them. See Your first project. |
| Repository | A Git repository in Forge. It belongs to an Orbit project and uses the project’s members. See Your first repository. |
| Runner | A program that you run on your own machine. It takes the jobs of one Forge project and runs each in a Docker container. See Runners. |
| Saved filter | A named query that you can share and star. Boards, plans, dashboards and subscriptions use it as their scope. See Saved filters and subscriptions. |
| Scenario | An isolated set of proposed changes in a plan. Nothing reaches the work items until you commit chosen fields. See Plans, teams and capacity. |
| Scheme | A reusable set of choices that projects share, such as work types, priorities and resolutions. See Custom fields, screens and schemes. |
| Service account | An account for automation that belongs to one site and never signs in. People own it, and it has its own API tokens. See Service accounts and tokens. |
| Site | Your company’s own address, <company>.orbit.inortix.com, with its own people, projects and data. See Organizations, sites and roles. |
| SLO | A service level objective in Pulse, with an error budget and burn-rate alerts. See Metrics, dashboards and SLOs. |
| Space | The Folio knowledge area of one project, with a page tree. See Your first space and page. |
| Sprint | A period of planned work. It is planned, active or completed, and a project has one active sprint unless it allows parallel sprints. See Boards, backlog and sprints. |
| Team | A named group of people that plans use for capacity. A team is shared across plans or belongs to one plan. See Plans, teams and capacity. |
| Version | A release of a project. It is unreleased, released or archived, and work items carry it as a fix version. See Project settings. |
| Work item | A unit of work with a key such as ORB-12: an epic, story, task, bug, sub-task or a type your administrators define. See Work items. |
| Workflow | The statuses a work item can have and the transitions between them. Changes are drafted and then published. See Workflows. |