concept
The top-level container for work. Every issue, saved filter, and activity log entry belongs to exactly one project. See Projects.
issue field
Where an issue is in its lifecycle:
Open, In Progress, or Closed. Every issue has exactly one.issue field
How urgent an issue is:
Low, Medium, or High. Every issue has exactly one (default Medium) — don’t confuse this with status.issue field
A tag describing what kind of work an issue is:
Bug, Feature, Performance, Design, UX, or Chore. An issue can have any number of labels, including none.issue field
The user who created an issue. Set automatically and never editable.
issue field
The user responsible for resolving an issue. Optional, and distinct from the creator.
views
The three interchangeable ways to look at a project’s issues. “Board” is Orbit’s name for the drag-and-drop Kanban view — not “Kanban” on its own. See Views.
concept
A named, reusable combination of search and filter criteria, scoped to one project. See Saved Filters.
concept
A per-user, in-app alert about something relevant to you (assignment, reassignment, a comment, an update). Not to be confused with the activity log. See Notifications.
concept
A per-project, backend-only audit trail of mutations. Distinct from notifications, and not currently viewable in the app’s UI. See Activity Log.
roles
Orbit’s two roles. The first account ever registered becomes admin; everyone after that is a member. There’s no “owner” or “guest” role, and today the role mostly affects onboarding, not permissions — see Roles and permissions.