Skip to main content
An issue is the unit of work in Orbit. Every issue belongs to one project, has an issue type, and moves through that type’s workflow.

​
Core fields

If you set both a start date and an end date, the end date must be on or after the start date.

​
Type and workflow

The issue type determines which workflow statuses are available. A Bug can therefore follow a different process from a Feature or an Incident. New issues start in the type’s initial status. See Configure workflows to manage statuses and allowed transitions. Changing an issue’s type also moves it to the new type’s initial status unless you explicitly choose a valid status from the new workflow. The available status changes can be limited by the workflow’s transition rules.

​
Create an issue

In List, select New issue to open the inline row. Enter a title, choose an issue type, and press Enter. The row previews that type’s initial status and creates the issue with Medium priority and no assignee. You can fill in the remaining details from the issue page afterward. Some types are only available for sub-issues. If a type is restricted to selected roles, Orbit checks your role when you create the issue. The type’s first template is applied automatically and can prefill the description and labels. See Issue types for template and required-field behavior.

​
Parent and sub-issues

Types that allow children show a Sub-issues section on the issue page. Select Add sub-issue, enter a title, choose an allowed type, and press Enter. A sub-issue must stay in the same project as its parent, and Orbit prevents circular parent chains. The issue header shows clickable ancestors for nested work. In List, parent and child rows form an indented tree that you can collapse or expand. See Configure hierarchy for the type-level rules.

​
Custom fields

An issue type can add short text, long text, number, date, choice, checkbox, and link fields. They appear in the issue sidebar and are saved individually. Required fields are marked with an asterisk.

​
Assignment and notifications

Assigning an issue to someone sends them an in-app notification. Reassigning notifies both the previous and new assignee. When an assigned issue changes, its assignee can also receive an update notification.

​
View and edit an issue

Each issue has a detail page with its description, properties, comments, children, and development links. With GitHub connected, the Development section can show linked pull requests and create branches or pull requests. Depending on your permissions, you can edit fields inline from this page or use the project’s List and Board views.

​
Delete issues

Issues can be deleted individually or in bulk from List. Deleting an issue also removes its comments, so use this action carefully.
Last modified on September 26, 2026