The repo represent a repository in the CI/CD.

The branch represent a branch in the CI/CD.

The Role object represents a role of a User.

The User object represents a User.

Organizations are the top level entity in the source application. Users are associated with an organization.

Licenses represent concepts like user seats in apps that support them

Workspaces represent concepts like teams, workspaces, projects in apps that support them

Comments represent the communication happening on a Ticket, both between a User and a Contact and the internal things like notes, private comments, etc. A Ticket can have one or more Comments.

Tags represent a common classification approach used in various ticketing systems. A Ticket may have one or more Tags associated with them.

Core resource which represents some work that needs to be carried out. Tickets are usually mapped to issues, tasks, work items, etc. depending on the underlying product.

Ticket Types represent the classification system used by the underlying products for Tickets. Some examples are bugs, feature, incident, etc.

Ticket Status represents the completion level of the Ticket. Some products provide customizing the Ticket Status.

Workspaces represent the top-level subdivision in a ticketing system. They usually have their own set of settings, tickets, statuses, priorities and users. Some of the usual terminologies used by the products for the top-level subdivision are projects, bases, spaces, workspace, etc. A Workspace could belong to an Organization.