ClickUp Airdrop

Experience hassle-free import of your ClickUp tasks into DevRev with DevRev's ClickUp Airdrop.

Supported objects

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

Spaces, Folders, and Lists are imported as custom fields within the issue/ticket object. The objects to import can be filtered based on their values if you select it so in the Mappings required phase.

ClickUp tasks are imported as issues by default. You can choose to have them imported as tickets if required.

For the sake of preserving existing structure, DevRev work items (issues or tickets) are created with the same hierarchical structure as the source tasks in ClickUp. That is, ClickUp tasks with child tasks become DevRev issues with child issues or tickets with child tickets.

However, while the DevRev UI allows you to create parent/child relationships between issues, you cannot do the same with tickets. If your workflow requires manual creation of parent/child relationships in DevRev work items, you should use issues. If that is not a requirement and tickets are preferred for another reason, you can specify tickets as the target for ClickUp tasks.

Import from ClickUp

Follow the steps below to import from ClickUp:

1. In Marketplace, search for ClickUp under the Import category and select the option for the ClickUp Airdrop.

2. In the snap-in config modal, click Install then go to Integrations > Imports in your settings left nav.

3. Click the Import import button and select the ClickUp tile in the Start import window.

4. Create a new connection to your ClickUp account, or use an existing connection if you already have one.

   While creating the connection, you are required to input a Subdomain field. This is a mandatory unique identifier used by Airdrop to group together imports from the same source system, and does not affect the import process.

   It is recommended to use the ID of the ClickUp workspace you want to import as the value of Subdomain.

5. Once the connection is established, select the ClickUp workspace you want to import and specify the DevRev part that should be used for any imported work. This initiates a bulk import of the selected site.

6. Click Map fields in the import row and configure filters, object mapping, or field mapping as necessary.

   If you want ClickUp tasks to become tickets rather than issues, map the task object to Works.Issue.

   While DevRev attempts to automatically map fields, you may be prompted to manually map indicated fields.

The duration of the import depends on the size of the ClickUp workspace and the data being imported. It can take seconds for a workspace with only a few dozen tasks to a few hours for a workspace with tens of thousands of items with many attachments. DevRev honors the ClickUp API rate limits and back-off and resumes automatically.

Post-import options

After a successful import, you have the following options available for the imported workspace:

• Sync to DevRev
  • Synchronize any modifications made in your ClickUp workspace with the corresponding items previously imported into DevRev. It also creates new items in DevRev for any new supported object type in ClickUp after the last sync or import.
• Periodic Sync
  • Synchronize new changes from ClickUp to DevRev on a periodic basis. The default frequency is once an hour.
• View Report
  • Access detailed information about the initial import and any subsequent syncs performed.
• Delete Import
  • Remove the import and all items that were imported from ClickUp into DevRev, you can use this option.
• Edit Connection
  • 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.

Sync to DevRev

After a successful import from a ClickUp workspace, you can choose to sync the imported data with DevRev. This feature imports any new tasks and comments and any changes made to previously imported items from ClickUp.

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

1. Go to Settings > Integrations > Imports.
2. Locate the previously imported project.
3. Select the ⇆ > ⇾ From Snap-ins to DevRev option.

A one-time sync 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.