Skip to content
Automation Squad
JCUSMade to order

Projects & operations

Jira issue created or moved → ClickUp task mirrored, status kept in step

Jira issues appear in ClickUp as tasks, and every status change follows within a minute.

Engineering lives in Jira and everyone else lives in ClickUp. This package mirrors one direction: when an issue is created in a chosen Jira project a ClickUp task is created in the matching list, and when the issue changes status, assignee or priority, the task follows. The ClickUp task ID is stored on the Jira issue, so updates always find the right task and reruns never duplicate. Failures are reported to a Slack channel with the issue key.

How it works

  1. J

    Trigger

    Issue created or updated in a chosen project (jira:issue_created and jira:issue_updated webhooks, registered by the n8n Jira Trigger node)

    Jira

  2. if

    Step 1

    Keep only the changes that matter

    Created events pass straight through. Updated events pass only when the changelog touches status, assignee or priority, so a description edit, a label change, or this package's own write-back of the ClickUp ID triggers no write.

  3. J

    Step 2

    Fetch the full issue

    One call to Jira's get-issue endpoint returns the summary, description, issue type, priority, status, the assignee's account ID and the ClickUp Task ID custom field this package adds to the project.

  4. if

    Step 3

    Map Jira values to ClickUp values

    A mapping table you fill in at setup translates each Jira status to a ClickUp status, Jira priority to ClickUp priority, and Jira account ID to ClickUp member ID (Jira Cloud can hide emails, so accounts are the key). Unmapped statuses leave the task alone.

  5. CU

    Step 4

    Create the task when the issue has no ClickUp ID

    The task lands in the list mapped to the Jira project with the issue key in its name, the description, priority and assignee set, and a Jira Key custom field plus a link back to the issue.

  6. J

    Step 5

    Write the ClickUp task ID back to the issue

    The new task's ID goes into the ClickUp Task ID custom field on the issue, and the task URL is added as a web link through Jira's remote-issue-link call. The field is how every later update finds its task.

  7. CU

    Step 6

    Update the existing task on status, assignee or priority change

    When the issue already carries a ClickUp ID, the task is updated in place with the mapped status, assignee and priority, and the change is noted as a comment on the task with the Jira actor's name.

  8. S

    Step 7

    Report any failed step to an error channel

    A companion error workflow catches any failed step and posts the issue key, the step that failed and the API response to a Slack channel you choose. A missed mirror is visible the same minute, not found in a stand-up.

What changes once it runs

  • A ClickUp task exists for every new issue in the mirrored projects within a minute of creation.
  • Status, assignee and priority changes in Jira show up on the ClickUp task without anyone copying them.
  • Each Jira issue links to its ClickUp task and each task links back, so both sides can find the other.
  • Re-delivered webhooks and reruns update the existing task instead of creating another.
  • Any failure is posted to Slack with the issue key and the API error the same minute.

What you get

  • Workflow export for n8n plus the companion error workflow, tested against a sample Jira project
  • One-off backfill workflow that creates tasks for the open issues already in the project
  • A guide to the Jira webhook, the custom field on each side and the ClickUp list mapping
  • Status, priority and assignee mapping table as an editable sheet
  • Video of an issue being created, moved and closed, with the task following
  • Rollback note: how to stop the mirror and what remains on each side

Before you start

  • Jira Cloud, with a site admin to register the webhook and add a short-text custom field to the project's edit screen, and an API token for that admin
  • ClickUp, Unlimited plan or above recommended: the Jira Key custom field this package adds counts against Free Forever's custom field limit
  • ClickUp statuses on the target list that cover the Jira workflow, or a decision on which Jira statuses collapse into one
  • Slack with permission to install an app and post to an error channel
  • An n8n instance Jira can reach over HTTPS, cloud or self-hosted, for the two webhooks

Built for

Questions before you buy

Does it work in both directions?
No. This package mirrors Jira into ClickUp only. A change made on the ClickUp task stays in ClickUp, and the next Jira update overwrites the mirrored fields. Two-way sync needs loop protection on both sides and is quoted as a separate build.
What about issues that already exist when I switch it on?
They are not touched until they change. The package ships with a one-off backfill workflow that walks the project with a JQL search and creates tasks for open issues, writing IDs back as it goes. Run it once after setup.
Our Jira workflow has statuses ClickUp does not have. What then?
Map them. The mapping sheet lets two or more Jira statuses point at one ClickUp status, and any Jira status you leave blank makes no change to the task. The setup guide walks through a typical eight-status Jira workflow against a five-status ClickUp list.
Does it mirror comments?
Not as shipped. The Jira Trigger node can subscribe to comment_created, and adding a ClickUp comment step is a short change described in the guide. It is left out by default because most teams do not want every engineering comment copied across.
Can it run on Make?
The seven steps with a write-back and a separate error path are built for n8n, so no, not as shipped. Make has Jira and ClickUp modules that cover the create and update calls; ask if you need that rebuild.

Nearby on the shelf

Whole catalog