feat(import): add clickup import - #332

🦋 Changeset detected

Latest commit: ba3b609

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Tested this in real project. Generally speaking — their exporting sucks. They only export break lines, and even that they managed to export as string \n rather than a real newline character.

Sharing my findings:

1. Line breaking doesn't work properly
2. Prevent null in the task description, when there is none
3. We have a lot in one Space, I'd also add a filter for "Folder name" and "List name"
4. There is a possibility in UI to export a separate list view, but it has different format of values and column names

Looks like they intentionally made it a pain point for people who want to migrate outside of their platform.

Thanks for reviewing this!

I noticed the \n issue too, but I did not catch the null task description, thanks for pointing that out.

I'll figure out if I can also do folder, but only if a space is specified, I don't know if I'm able to have dynamic options, but we'll see. The complicated way I did it was import the CSV into a Excel file, filter to the space I want, then replaced the "Space" with the Folder/list I wanted, then used that as the CSV.

I can add a different type of importing too, ClickUp (CSV) is what I currently have, if there's a different export I'll try that as well and support it separately.

I'm going to consider this PR abandoned and review how close it was to getting over the finish line. My org is looking to complete a ClickUp -> Linear migration, and moving our tickets into Linear is the biggest hurdle. I might be able to refactor into a workable state in the process of importing my own org's data.

We recommend using the CSV importer for ClickUp at this time:
https://linear.app/docs/import-issues#trello-pivotal-tracker-or-clickup

Note both #220 and #332 only pull info from a csv export from clickup, which means you won't get task comments.
Same goes when you use the CSV importer btw.

I'm quite certain that to import task comments you'll need to connect to the Clickup API.

To capture custom fields I can recommend converting those to label groups. For example a "Specialization" field (with Front-end or Back-end etc), could be converted into an additional tag like Specialization/Front-end. Keep in mind that label groups are exclusive, so for example you can't store multiple Specializations. And the labels can't contain /'s.

I'm going to go ahead and close this since I am unfortunately mostly done with both platforms (though I hope to return to linear!) Feel free to improve on this or rewrite your own. I do agree with Peter that the API should be used instead of an export, but a CSV is ultimately easier. Hopefully we will have native import one day!