Skip to content
Notis

Keep a Jira campaign issue aligned with the latest brief

When campaign details change, update the Jira issue from the revised brief instead of letting two versions drift apart.

Trigger

Webhook received

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

Action

Edit Issue

Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.

Why this helps

Teams can keep working from stale campaign details after a brief has changed.

  • Bring revised supplied details into the existing issue.
  • Keep campaign decisions attached to ongoing work.
  • Avoid creating duplicate issues for simple brief changes.

Setup

Build it in a few focused steps.

  • 1Connect BulkPublish and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it.
  • 3In one instruction, tell Notis how to identify the existing issue and update it from each revised brief while preserving unrelated issue details.
  • 4Choose the webhook trigger and select where run reports should go.
  • 5Test with one real revised brief and Jira issue.

Questions about this workflow

Will it know which issue to update?

The instruction or webhook context must provide a reliable issue key or other way to identify the existing Jira issue.

Can it preserve unrelated fields?

Tell Notis to change only the relevant supplied details. Review the first real example to confirm the update matches your intent.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

BulkPublish 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

Add Watcher to Issue

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

ActionInstant

Assign Issue

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

ActionInstant

Bulk Create Issues

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

ActionInstant

Create Issue

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

ActionInstant

Link Issues

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

ActionInstant

Create Project

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

ActionInstant

Connect any two apps with Notis in the middle.

BulkPublish 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.