Linear Airdrop
To ease the transition from Linear issues to DevRev, you can import and sync Linear issues with DevRev. There are currently two versions of the Linear Airdrop integration available:
Legacy Linear (deprecated)
The legacy Linear Airdrop is deprecated and will be removed soon. While existing imports continue to function for some time after removal, no new imports can be created once the feature is removed. It is strongly recommended to use the new Linear Airdrop for all new implementations.
There is no automatic migration path from legacy to new Linear Airdrop. To switch to the new version, you must delete your existing import and create a new one using the new Linear Airdrop.
New Linear Airdrop
The new Linear Airdrop provides enhanced functionality including bi-directional synchronization between DevRev and Linear.
Key differences from legacy version
- Bi-directional Sync: Changes can be synchronized in both directions between DevRev and Linear
- Enhanced Field Mapping: Improved field mapping capabilities.
For more information, refer to the Linear Airdrop snap-in on the DevRev marketplace.
Supported objects
The following is a list of Linear objects and their corresponding DevRev equivalent. Those marked as Supported are eligible for import.
Linear OAuth Application
- Go to Settings in your Linear Workspace.
- Click API > add OAuth Application > create New Application.
Only Admins can create applications.
- Once the application is created, scroll down to find the Developer Token section.
- Click Create & copy token > Application. Token is copied to clipboard.
- Store the token securely, as you need it during the connection setup in the Linear snap-in.
Importing from Linear
For best results, Airdrops should be done using an administrator account on the external source. This ensures all necessary permissions are available to complete the import successfully.
- Go to Settings > Snap-ins and install Linear.
There may be an existing Linear Issues already added. If so, Add the other.
-
Go to Settings > Airdrops and click Airdrop.
-
Under the Snap-ins tab, select Airdrop Linear Snap-in.
If this isn't available, install the snap-in as described in step 2. Do not select the legacy Linear under "Native to DevRev".
-
Follow the prompt and create a connection, providing the Linear Application Token and the Linear Workspace name when creating a new connection.
-
A recipe is presented where you select what data to import and how to map it. The recommended values are preselected.
Post import options
After a successful import, you have these options added for an imported project:
- Sync Snap-ins to DevRev
- Write any modifications made in Linear to the corresponding work item in DevRev.
- Create new work items in DevRev for any new issues created in Linear after the last sync or import.
- Sync DevRev to Snap-ins
- Write any modifications made in DevRev to the corresponding work item in Linear.
- Create new work items in Linear for any new issues created in DevRev after the last sync or import.
- View report
- View details of the initial import and any syncs performed afterward.
- Periodic Sync
- By enabling this option, you can automatically sync new changes from Linear to DevRev periodically. The default frequency is once an hour.
- Delete import
- Removes the import and all work that was imported into DevRev from the Linear team.
- Edit connection
- Changes the connection used for any subsequent action (that is, Sync). This is helpful if a connection goes stale or the user who established it, is no longer available.
Legacy Linear Airdrop
This section describes the legacy Linear Airdrop functionality. This version is deprecated and is being removed soon. Please use the new Linear Airdrop for all new implementations.
Supported objects
The following is a list of Linear objects and their corresponding DevRev equivalent. Those marked as Supported are eligible for import.
Importing from Linear
For best results, Airdrops should be done using an administrator account on the external source. This ensures all necessary permissions are available to complete the import successfully.
To import your Linear issues, go to Settings > Integrations > Airdrops then select **Start Airdrop* or **Airdrop*.
From there, create a new connection to your Linear workspace or use an existing connection if you already have one. Once the connection is established, select the team's issues you wish to import. This performs a bulk import of the selected issues. DevRev tries to automatically and sensibly map your fields to corresponding fields in DevRev, but it may prompt you on how you want to map certain fields.
Post import options
After a successful import, you have these options added for an imported project:
- Sync to DevRev
- Write any modifications made in Linear to the corresponding work item in DevRev.
- Create new work items in DevRev for any new issues created in Linear after the last sync or import.
- View report
- View details of the initial import and any syncs performed afterward.
- Delete import
- Removes the import and all work that was imported into DevRev from the Linear team.
- Edit connection
- Changes the connection used for any subsequent action (that is, Sync). This is helpful if a connection goes stale or the user who established it, is no longer available.
Sync to DevRev
After a successful issue import from a Linear team, you have the sync to DevRev option. The sync to DevRev feature airdrops any new issues and any new changes to previously imported issues.
To perform a one-time sync to DevRev, go to Settings > Integrations > Airdrops and find the previously imported project and select the Sync > ⇾ DevRev option.
Historical Airdrops
To view currently running and previous Airdrops from various sources, do the following:
- Go to Settings > Integrations > Airdrops.
- Select the import you want to view.
- Click on the context menu (⋮) and select View Report.
Periodic sync
After successfully importing to DevRev, you have the option to enable a periodic sync. This allows for automatic synchronization with DevRev on a regular basis. By default, the sync occurs once an hour.
To configure periodic sync, follow these steps:
- Go to Settings > Integrations > Airdrops.
- Locate the previously imported project.
- Select the ⋮ > Set Periodic Sync option.
The Enable automations for synced items setting is optional and can be activated during periodic sync configuration. When enabled, newly created or updated items trigger events, which can initiate webhooks, notifications, Snap-ins, and other processes, as if the events originated directly in DevRev.
If this setting is disabled, updates will not trigger any event-driven processes. This behavior applies only to periodic syncs; no events are triggered during a first-time import or manual sync to or from DevRev.
Delete import
This deletes any content created by the import, including users and works.
An import and all the content it creates can be deleted from DevRev. This can be useful when running POCs or to change the recipe used during the import. Once an import has been deleted, all the content it created gets deleted, even if they were modified in DevRev. It's possible to import the project again after its deletion.
To delete an import and all the content it created, go to Settings > Integrations > Airdrops, find the previously imported project, and select ⋮ > Delete Import.
