GitHub Issues Airdrop

To ease the transition from GitHub issues to DevRev, you can choose to import GitHub issues into DevRev.

Supported objects

The following is a list of GitHub objects and their corresponding DevRev equivalent. Those marked as Supported are eligible for import.

Importing from GitHub

Follow the steps below to import from GitHub:

For best results, imports should be done using an administrator account on the external source. This ensures all necessary permissions are available to complete the import successfully.

1. Go to Settings > Integrations > Imports and click Start Import or Import.
2. Create a new connection to your GitHub account, or use an existing connection if you already have one.
3. Once the connection is established, select the GitHub repositories you want to import and specify the DevRev part where the imported issues should be created. This initiates a bulk import of the selected repositories.
4. DevRev makes an effort to automatically map the fields from GitHub to corresponding fields in DevRev. However, you may be prompted to manually map certain fields if needed.

The duration of the import depends on the number of issues being imported. It can take seconds for a few dozen issues to hours for tens of thousands of issues with many attachments. DevRev honors the GitHub API rate limits, it backs off and resumes automatically.

Post import options

After a successful import, you have these options added for each imported repository:

• Sync to DevRev
  • This option allows you to synchronize any modifications made in GitHub with the corresponding items previously imported into DevRev. It also creates new items in DevRev for any new issues or users created in GitHub after the last sync or import.
• Periodic Sync
  • By enabling this option, you can automatically sync new changes from GitHub to DevRev periodically. The default frequency is once an hour.
• View Report
  • This option allows you to access detailed information about the initial import and any subsequent syncs performed.
• Delete Import
  • If you wish to remove the import and all items that were imported from GitHub into DevRev, you can use this option.
• Edit Connection
  • Use this option to change the connection used for any subsequent actions. It can be helpful if a connection becomes inactive or the user who established it is no longer available.

GitHub issue import recipe

The following recipe is used to import GitHub issues into DevRev issues.

Transient users are created in DevRev for the GitHub assignees and creators.

Sync to DevRev

After a successful import from a GitHub repository, you can choose to sync the imported data with DevRev. This feature imports any new issues and any changes made to previously imported issues from GitHub.

To perform a one-time sync to DevRev, follow these steps:

1. Go to Settings > Integrations > Imports.
2. Locate the previously imported repository.
3. Select the ⇆ > ⇾ From GitHub to DevRev option.

Please be aware that this may override fields in previously imported items, even if they were modified in DevRev.

Historical imports

To view currently running and previous imports from various sources, do the following:

1. Go to Settings > Integrations > Imports.
2. Select the import you want to view.
3. 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:

1. Go to Settings > Integrations > Imports.
2. Locate the previously imported project.
3. 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 > Imports, find the previously imported project, and select ⋮ > Delete Import.