Linear
Visualize your Linear organization, projects, teams, and users in the JupiterOne graph and monitor changes to Linear entities by leveraging JupiterOne alerts.
- Installation
- Authorization
- Data Model
- Types
Installation
The integration connects to Linear's GraphQL API using a personal API key to ingest your Linear organization, teams, projects, users, and issues into JupiterOne.
Before you begin, you will need a Linear personal API key. In Linear, admins choose whether members can create their own API keys from Settings > Administration > API > Member API keys. Admins and permitted members can then create personal API keys. For more information, see Linear's API documentation.
Prerequisites
- A Linear personal API key created by a user who is permitted to create one.
- The key must be granted at least the Read permission.
- The key's access must cover the team or teams whose data you want to ingest. Ingested data is bounded by the key owner's own Linear permissions and team access.
Configuration in Linear
- In Linear, go to Settings > Account > Security & Access (or visit linear.app/settings/account/security).
- Create a personal API key. When creating the key, grant it at least the Read permission, and limit its team access to the teams whose data you want JupiterOne to ingest.
- Copy the API key and save it for use within JupiterOne.
Configuration in JupiterOne
To install the Linear integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Linear. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
The Account Name used to identify the Linear account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen the Tag with Account Name toggle is enabled. -
A Description to assist in identifying the integration instance, if desired.
-
A Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration. -
The Access Token field, in which you enter the Linear personal API key you created.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data about your Linear environment within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Permissions
IAM permissions that must be granted to the integration principal for data ingestion.
Show Permissions (1)
Read
Endpoints
API endpoints that the integration makes requests to.
Show Endpoints (1)
https://api.linear.app/graphql
Documentation Links
Links to provider documentation relevant to setup and configuration.
Show Documentation Links (2)
Per-Step Breakdown
Detailed authorization requirements for each ingestion step.
Show all steps (1)
| Step | Permissions | Endpoints |
|---|---|---|
| Relate Projects to Users | Read | https://api.linear.app/graphql |
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Issue | linear_issue | Record, Issue |
| Organization | linear_organization | Account |
| Project | linear_project | Project |
| Team | linear_team | Team, UserGroup |
| User | linear_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
linear_issue | ASSIGNED | linear_user |
linear_issue | CONTAINS | linear_issue |
linear_organization | HAS | linear_team |
linear_project | HAS | linear_user |
linear_project | HAS | linear_issue |
linear_team | HAS | linear_project |
linear_team | HAS | linear_user |
linear_team | HAS | linear_issue |
linear_user | CREATED | linear_issue |