Skip to content
Notis

Resume browser debugging when a Jira issue changes

Keep the investigation close to the issue: a change can prompt Notis to fetch debug links for a running browser session.

Trigger

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

Action

Retrieve Session Debug URLs

Tool to retrieve live debug urls for a specific session. use when you need to connect to a running session for debugging.

Why this helps

When a bug changes status or details, the browser session and its live debugging links can be difficult to find again.

  • Make active browser sessions easier to reopen for investigation.
  • Reduce time spent searching for debug access.
  • Prompt a useful follow-up when an issue is updated.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Browserbase tool once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name.
  • 3Tell Notis to retrieve live debug URLs for the Browserbase session associated with an updated issue, using a session id available to the automation.
  • 4Pick the Jira Updated Issue trigger, then choose where run reports should go.
  • 5Test with one real issue and an available session id, then review the run report.

Questions about this workflow

Does Jira provide the Browserbase session id automatically?

The Jira event is an issue update. The session id must be available to the automation, for example in the issue details or other supplied context.

Will this create a new browser session?

No. It retrieves debug URLs for a specific running session, so the automation needs that session id.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Jira triggers

Browserbase tool actions

Recurring trigger

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

TriggerScheduled

Create a new browser context

Tool to create a new browser context. use when you need to obtain upload credentials for a custom user-data-directory in a project.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Retrieve a browser context

Tool to retrieve details of a specific browser context. use when you have a context id and need its metadata.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Update Browser Context

Tool to update a specific browser context. use when you need fresh upload url and encryption details for an existing context, after obtaining a valid context id.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Create Browser Session

Tool to create a new browser session. use when you need an isolated browser context before performing any page interactions.

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Retrieve a browser session

Tool to retrieve details of a specific browser session. use when you have a session id and need its metadata (status, urls, timestamps).

ActionInstant

Retrieve Session Debug URLs

Tool to retrieve live debug urls for a specific session. use when you need to connect to a running session for debugging.

ActionInstant

Download Session Artifacts

Tool to download files from a specific session. use after session completion to retrieve all generated artifacts in a zip archive.

ActionInstant

Retrieve Session Logs

Tool to retrieve logs of a specific session. use after actions in a session to inspect network events and data exchange.

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Browserbase tool, 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 Browserbase tool.