ClickUp + Jira

Learn about Unito's ClickUp-Jira integration and which fields it can sync.

In this article:

In addition to these standard fields, ClickUp has a number of custom fields that can be mapped to Jira fields:

ClickUp's Date custom field can be mapped to the Due date, start date, sprint start date, or sprint end date fields in Jira.
ClickUp's Text and Long Text custom fields can be mapped to the Description, time spent, estimated duration, sprint, sprint start date, sprint end date, issue type, labels, epic, components, priority, fix versions, affected versions, link to issue, or issue number fields in Jira.
ClickUp's Number custom field can be mapped to the original estimated duration, remaining estimated duration, start date, or time spent fields in Jira.
ClickUp's Dropdown custom field can be mapped to the components, fix version, issue type, labels, or priority fields in Jira
ClickUp's Label custom field can be mapped with Jira labels.
ClickUp's URL custom field can be mapped to the affected version, components, epic, fix versions, issue number, issue type, labels, originated estimated duration, remaining estimated duration, priority, time spent, start date, sprint start date, or sprint end date fields in Jira.

Filter ClickUp tasks by status: With this integration, you can only do this with task status. You could use this feature to make sure Jira issues only show in ClickUp when they're in progress, for example.
Filter by issue type: Choose exactly which issue types sync from Jira.
Choose default Jira issue type: Control what issue type is used when new tasks originate in ClickUp.
Add Jira issue number as prefix: Easily reference Jira issues by automatically adding Jira issue numbers to task titles.