Skip to content
Notis

Record CircleCI recovery in Jira

When a later CircleCI run succeeds, help the team see that recovery in the Jira issue tracking the earlier failure.

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

A fixed build can leave stale Jira context behind, so people spend time checking whether the failure still exists.

  • Bring recovery evidence into the related Jira issue.
  • Reduce time spent rechecking resolved CI failures.
  • Keep updates grounded in runs and issue links that are available.

Setup

Build it in a few focused steps.

  • 1Connect CircleCI and Jira once in Notis.
  • 2Create an automation in plain language or in Automations, New Automation.
  • 3In one instruction, ask Notis to find Jira issues linked to earlier CircleCI failures and update a clearly related issue when a later run shows success.
  • 4Pick a recurring Notis schedule and choose where run reports go.
  • 5Test with one recovered failure and verify the issue update reflects the available run evidence.

Questions about this workflow

Does a successful later run automatically resolve the Jira issue?

No. This workflow records the recovery in the issue. If you want a status change, describe that explicitly and only when the available evidence supports it.

What if there is no clear link between the run and issue?

Have Notis report the successful run for review and leave Jira unchanged when it cannot establish a clear relationship.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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