Skip to content
Notis

Keep Jira issues current with campaign changes

Bring new campaign context into related Jira work during a regular review.

Trigger

Recurring schedule

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

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

Existing Jira tasks can go stale when campaign details change after the ticket was created.

  • Refreshes existing issues when available campaign information changes their context.
  • Keeps campaign-related work aligned with current details.
  • Avoids creating a duplicate issue for every update.

Setup

Build it in a few focused steps.

  • 1Connect Amcards and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it for campaign updates.
  • 3In one instruction, tell Notis how to identify the related Jira issue and update it only when the campaign information changes relevant to the work.
  • 4Pick a recurring schedule and choose where run reports should go.
  • 5Test with one real campaign update and verify the intended Jira issue changes appropriately.

Questions about this workflow

How does Notis find the related Jira issue?

Specify how the available campaign information identifies the issue, such as a Jira key included in the campaign context. If no reliable link is available, provide one.

Will it update every related issue on every run?

Instruct Notis to update only when relevant information has changed. The source must expose enough information to determine that change.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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