Skip to content
Notis

Transition Jira issues from ClickUp status changes

When work moves forward in ClickUp, prompt Notis to move the related Jira issue along too.

Trigger

Task Status Updated

Triggers when a task's status changes. `changes[]` carries `StatusChange` entries only — ClickUp pre-filters server-side by event type. Lower traffic than subscribing to `CLICKUP_TASK_UPDATED` and pattern-matching `StatusChange`.

Action

Transition Issue

Transitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.

Why this helps

Updating the same work status in two tools creates extra follow-up and mismatched views.

  • Reduce repeated status updates across tools.
  • Keep Jira workflow states current when ClickUp status changes.
  • Use one prompt to explain how status changes should translate.

Setup

Build it in a few focused steps.

  • 1Connect ClickUp and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it for the status change.
  • 3Tell Notis how to find the related Jira issue and which Jira transition to use for each relevant ClickUp status.
  • 4Pick the ClickUp Task Status Updated trigger and choose where run reports should go.
  • 5Test with one real status change and review the Jira transition.

Questions about this workflow

Does the trigger include status-change details?

Yes. The event carries status change entries and is pre-filtered for task status updates.

How does Notis know which Jira issue to transition?

Tell Notis how to identify the related issue in your prompt, for example by a Jira key included in the task. If that reference is not available, provide another reliable matching instruction.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Clickup to Jira. A trigger fires from one place; an action lands in another.

Clickup triggers

Jira actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

Folder Created

Triggers when a new Folder is created.

TriggerInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Folder Deleted

Triggers when a Folder is deleted.

TriggerInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

Folder Updated

Triggers when a Folder is updated (renamed, content edited, etc.).

TriggerInstant

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

List Created

Triggers when a new List is created.

TriggerInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

List Deleted

Triggers when a List is deleted.

TriggerInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

List Updated

Triggers when a List is updated (renamed, content edited, etc.).

TriggerInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

Connect any two apps with Notis in the middle.

Clickup and Jira, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Jira.