Skip to content
Notis

Keep Jira aligned with Bannerbear template changes

Pass template updates into Notis so the related ticket reflects the latest creative change.

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

Template edits can leave implementation tickets describing work that has already changed.

  • Refresh ticket details after a template change.
  • Preserve the connection between creative work and its Jira task.
  • Cut manual ticket cleanup after edits.

Setup

Build it in a few focused steps.

  • 1Connect Bannerbear and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name the template update workflow.
  • 3In one instruction, ask Notis to update the specified Jira issue with the provided template change details.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one real template update and its related issue.

Questions about this workflow

What should the webhook include?

Include the Jira issue key or id and the Bannerbear template change details that should inform the update.

Can Notis infer details that are missing?

Notis can analyze returned data, but any change details not supplied by Bannerbear or the request must be provided by you.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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