Skip to content
Notis

Keep Jira issue details aligned with browser findings

When a browser session clarifies what is happening, use the finding to improve the existing Jira issue instead of starting over.

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

Tickets drift from reality when new reproduction details never make it back into Jira.

  • Add newly observed reproduction details to the right issue
  • Keep ticket summaries grounded in browser results
  • Avoid duplicate issues when an existing issue already covers the problem

Setup

Build it in a few focused steps.

  • 1Connect Browserbase and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it.
  • 3Describe the outcome: match each incoming browser finding to an existing Jira issue and update its description with verified new reproduction details, creating no issue if no confident match exists.
  • 4Pick a webhook as the trigger and choose where run reports go.
  • 5Test with one real browser finding and an existing Jira issue, then review the update.

Questions about this workflow

Does this create new Jira issues?

No. This workflow updates a relevant existing issue. Ask Notis to report cases where no confident match is found.

Can it change priority too?

You can instruct Notis to update priority when the session data supports that decision. State the criteria clearly.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Browserbase tool 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.

Browserbase tool 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.