Jira Import - Preserve Task IDs
complete
J
Jared Albers
It would be great to be able to preserve the Jira ticket number on import. In other words, have it map to ClickUp's custom Task IDs.
Similarly, it would be great to be able to support TaskIDs at the Folder level, not just the Space level.
As per ClickUp's Hierarchy diagram (https://clickup.com/hierarchy-guide), a Jira Project = ClickUp Folder.
So I'd expect to be able to have custom TaskIDs at the Folder Level.
Log In
Luci N.
complete
Hey, everyone! We are thrilled to share that there is the ability to preserve the ID of a Jira issue on import!
When importing from Jira into ClickUp, the Jira ID is imported into a new, separate, Text Area (long text) Custom Field called 'Jira ID'.
As always, please let us know what we can improve by voting and commenting on existing posts, or creating a new Feature Request when needed!
D
Dev Sen
Hi. We were investigating migrating from JIRA to ClickUp, but Clickup doesn't currently have a few critical features, which are blocking our adoption. Namely: 1) the ability to preserve JIRA ticket numbers on import (total blocker); 2) ability to auto-number/ID tickets in ClickUP, as JIRA does (again total blocker); 3) ability to "intelligently" migrate JIRA tickets preserving the statuses and folders the tickets are in, alternately the ability to migrate single JIRA folders/projects at a time (partial blocker).
Since your marketing materials make a lot of claims about replacing JIRA with ClickUp it would be nice to have the actual functionality in place.
For us at the moment, ClickUP is, sadly, not an alternative to JIRA. I hope you quickly implement these critical/blocking features, so that current JIRA users actually can switch.
Good luck!
Shaquille Payne
Merged in a post:
Allow importing Jira Issue IDs as Custom Task IDs
Brent Evans
[from a support ticket]
D
Duncan Brown
Just a follow-up on this. We're presently a JIRA shop and this would block us migrating projects into CU.
D
Daniel Heighton
I honestly don't care about the custom task ids at all. In theory the 'friendly' name is easier to remember then the random 5 digits, but in practice it really isn't. I don't know what DATAENTRY-902 and DATAENTRY-953 are. There's a few tickets I have memorized because of how often they got used in a short period, but not many. So in practical effect, I have no plans to even use custom task ids.
My concern here is just on code integration. So my preferred version of this is that I can configure the code integration to look at a custom field alongside the task id, and custom id. So in the case of imported data, I can just point the code integration at the custom field holding the jira task id, and now all of my old code linkups work.