Skip to content
Notis

Show Jira blockers in ClickUp task dependencies

Make a clear blocker relationship visible in the ClickUp task flow.

Trigger

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

Action

Add dependency

Adds a 'waiting on' or 'blocking' dependency to a task, requiring either `depends on` (task becomes waiting on) or `dependency of` (task becomes blocking), but not both; `team id` is required if `custom task ids` is true.

Why this helps

A dependency mentioned in Jira can be overlooked when related work is tracked in ClickUp.

  • Make a supplied blocker relationship visible in ClickUp.
  • Help teammates understand what is waiting on other work.
  • Reduce manual dependency updates.

Setup

Build it in a few focused steps.

  • 1Connect Jira and ClickUp once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3Tell Notis how to find both related ClickUp tasks and interpret the blocker direction from the Jira details.
  • 4Pick the Updated Issue trigger for the Jira project and choose where run reports go.
  • 5Test with one real issue update containing a clear dependency and review the resulting link.

Questions about this workflow

Will this infer blockers that Jira does not state?

No. The workflow should use a relationship present in the returned details or supplied by you, and report when direction is unclear.

Can a ClickUp dependency have both directions at once?

No. The action accepts either a task that this task depends on or a task this task blocks, not both in one request.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Jira triggers

Clickup actions

Recurring trigger

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

TriggerScheduled

Add dependency

Adds a 'waiting on' or 'blocking' dependency to a task, requiring either `depends on` (task becomes waiting on) or `dependency of` (task becomes blocking), but not both; `team id` is required if `custom task ids` is true.

ActionInstant

Webhook trigger

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

TriggerInstant

Add guest to folder

Adds a guest to a folder with specified permissions; requires a clickup enterprise plan.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Add guest to list

Shares a clickup list with an existing guest user, granting them specified permissions; requires the workspace to be on the clickup enterprise plan.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Add guest to task

Assigns a guest to a task with specified permissions; requires clickup enterprise plan, and `team id` if `custom task ids` is true.

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Add tags from time entries

Associates a list of specified tags with one or more time entries within a given team (workspace).

ActionInstant

Add tag to task

Adds an existing tag to a specified task; team id is required if custom task ids is true.

ActionInstant

Add task link

Links two existing and accessible clickup tasks, identified by `task id` (source) and `links to` (target).

ActionInstant

Add task to list

Adds an existing task to an additional clickup list; the "tasks in multiple lists" clickapp must be enabled in the workspace for this.

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Clickup, 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 Clickup.