Skip to content
Notis

Refresh Jira tickets with Ayrshare campaign context

Give open work a scheduled context refresh using Ayrshare information available to Notis, so useful campaign details do not stay in a separate tool.

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

Open Jira tickets can become disconnected from the social campaigns and reports that provide their context.

  • Keep relevant campaign context with existing Jira work.
  • Reduce manual ticket maintenance during recurring reviews.
  • Refresh only tickets identified by the instruction and available data.

Setup

Build it in a few focused steps.

  • 1Connect Ayrshare and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it for the ticket refresh.
  • 3In one instruction, ask Notis to update specified existing Jira tickets with relevant available Ayrshare campaign context.
  • 4Choose a recurring schedule as the trigger and select where run reports should go.
  • 5Test with one real ticket and confirm the update preserves its useful existing details.

Questions about this workflow

Can this find every ticket related to an Ayrshare campaign automatically?

Only if the available data or instruction identifies those tickets. The listed Jira update action does not establish a hidden relationship.

What happens if the campaign context is unavailable?

Notis can only use information made available to the automation, so provide the needed context or treat it as missing.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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