Keep Jira issue context on the existing ClickUp task
Bring the new issue details into the ClickUp task your team already uses.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Create task comment
Adds a comment to a clickup task; `team id` is required if `custom task ids` is true.
Why this helps
Related information can be split across tools even when a ClickUp task already tracks the work.
- Keep related issue context alongside the task.
- Reduce switching between Jira and ClickUp.
- Preserve a readable source reference for follow-up.
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 identify the existing ClickUp task and what issue context to include in its comment.
- 4Pick the New Issue trigger for the Jira project and choose where run reports go.
- 5Test with one real Jira issue and review the comment on the matched task.
Questions about this workflow
Does this create the ClickUp task too?
No. It comments on an existing task, so the instruction needs a reliable way to identify that task.
What should the comment include?
Specify the useful issue details and source reference you want included. Notis can only use information available from the event or your instruction.
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.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add guest to folder
Adds a guest to a folder with specified permissions; requires a clickup enterprise plan.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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.
New Project
Triggered when a new project is added in Jira
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.
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.
Add tags from time entries
Associates a list of specified tags with one or more time entries within a given team (workspace).
Add tag to task
Adds an existing tag to a specified task; team id is required if custom task ids is true.
Add task link
Links two existing and accessible clickup tasks, identified by `task id` (source) and `links to` (target).
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.
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.