Linear (Edge)

Configure Linear as a Source in your Pipeline

Perform the following steps to configure your Linear Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Linear.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Linear Source.

   • In the Connect to Linear section, specify the following:

     • API Key: The personal API key that you created in Linear.

6. Click Test & Continue to test the connection to your Linear Source. Hevo checks that Linear accepts the API key by reading the details of the user who created the key. If the key does not have the permission to read this data, the test fails with a permission error. Once the test is successful, you can proceed to set up your Destination.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests all the data of the selected objects. For most objects, this includes archived records, which Hevo marks as deleted.

• Incremental Data: Once the historical load is complete, Hevo ingests data as per the sync frequency:

  • For the following objects, Hevo ingests the records created or updated since the previous run, based on the updated_at field: Attachment, Comment, Customer, Customer Request, Cycle, Initiative, Issue, Issue History, Label, Project, Project Label, Project Milestone, Project Update, and Users.

  • For all the other objects, Hevo ingests the entire data in each run.

  Child objects, such as Issue Label, are ingested along with their parent object.

Linear limits the number of API requests and the query complexity that a user’s API keys can use in an hour. Read Rate limiting. If a limit is reached, Hevo waits for a short time for the limit to reset. If the limit does not reset in that time, Hevo does the following:

• During the historical load: Hevo loads the data read so far without deleting or replacing any existing data, displays a warning for the object and its child objects, and reads the object again automatically. For the objects ingested incrementally, Hevo resumes reading from the record at which it stopped.

• During incremental runs: For the objects ingested incrementally, Hevo loads the data read so far, displays a warning for the object and its child objects, and in the next run, resumes reading from the record at which it stopped. For the objects ingested in full in each run, Hevo does not load any data for the object in that run and reads it again in the next run.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

The primary key of most objects is id. The following objects use other primary keys:

• Attachment Metadata: attachment_id and name.

• Initiative History: id and initiative_id.

• Issue History: id and issue_id.

• Issue Label: issue_id and index.

• Issue Subscriber: issue_id and subscriber_id.

• Label Children: label_id and label_children_id.

• Project External Link: project_id and id.

• Project Label Children: project_label_id and child_id.

• Project Label Project: project_id and project_label_id.

• Project Member: project_id and member_id.

• Project Update Comment: project_update_id and comment_id.

• Project Update Reaction: project_update_id and id.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---