Skip to content
Notis

Move Jira issues forward when tests confirm recovery

Once a later run meets your recovery criteria, let Notis transition the related Jira issue and report the evidence.

Trigger

Recurring schedule

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

Action

Transition Issue

Transitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.

Why this helps

Teams can leave resolved performance issues open because confirming recovery and updating Jira takes another manual step.

  • Close the loop after a verified recovery
  • Keep Jira workflow state in step with test evidence
  • Reduce manual status updates after successful reruns

Setup

Build it in a few focused steps.

  • 1Connect BlazeMeter and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, then name it and add an instruction.
  • 3Tell Notis the supplied recovery condition and which Jira issue to transition when a new BlazeMeter result satisfies it.
  • 4Choose a recurring schedule and where run reports should go.
  • 5Test with one real recovered result and confirm the intended Jira transition is available and applied.

Questions about this workflow

Will the workflow transition an issue based on any passing test?

Only if your instruction defines that as the recovery condition. Specify the relevant test, threshold, and issue relationship.

What if Jira has no matching transition?

Notis should report that the transition was unavailable and leave the issue state unchanged.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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