Check Bugsnag event activity when Jira issues change
A change to status or ownership can be a cue to revisit the evidence. Ask Notis to check Bugsnag events and summarize useful activity for the updated issue.
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
List Events on Project
Tool to list events for a project. use when you need to retrieve all error occurrences (events) for a given project after confirming its id. example: "list events for project 515fb9337c1074f6fd000003".
Why this helps
Incident updates can happen without anyone checking whether Bugsnag event activity has changed or adds useful context.
- Pair an issue update with a fresh look at Bugsnag events.
- Give owners a concise investigation summary after meaningful Jira changes.
- Highlight when issue context is insufficient to connect it to event activity.
Setup
Build it in a few focused steps.
- 1Connect Jira and Bugsnag once in the Notis portal.
- 2Create an automation for Bugsnag event review on Jira updates.
- 3Tell Notis to review Bugsnag events for the relevant project when an issue changes and summarize activity that may relate to the issue.
- 4Pick Jira Updated Issue as the trigger and choose where run reports should go.
- 5Test with one real updated issue and check that the report is actionable.
Questions about this workflow
Does this run for Jira comments?
No. The provided Jira Updated Issue trigger does not fire on comment activity.
Will it know whether events are related to the issue?
Notis can compare event data with details included in the Jira issue. Supply the identifiers or conventions your team uses, and expect it to flag missing details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Bugsnag. A trigger fires from one place; an action lands in another.
Jira triggers
Bugsnag actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk Update Errors
Tool to bulk update multiple errors in a project. use when batching identical updates across many errors.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Configure Integration
Tool to configure a new integration for a bugsnag project. use after selecting integration key and preparing credentials.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Invite Collaborator
Tool to invite a collaborator to an organization. use when you need to add a new user by email to grant them access. ensure the organization id is correct before calling.
New Project
Triggered when a new project is added in Jira
Create Custom Event Field
Tool to create a custom event field for a project. use after confirming the project id to add a new filterable field. example: "create a field 'user.id' mapping to 'metadata.user.id' for project 515fb..."
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.
Create Saved Search
Tool to create a new saved search for a project. use when you need to persist a set of filters and sort order as a saved search for a project after confirming project details.
Delete All Errors in a Project
Tool to delete all errors in a project. use when you need to remove all error and event data for a given project. use with caution after confirming the project id, as this action is irreversible and requires project owner or organization administrator permissions.
Delete Collaborator
Tool to remove a collaborator from an organization. use when revoking collaborator access after confirming both organization and collaborator ids. requires organization administrator privileges.
Delete a configured integration
Tool to delete a configured integration. use when you need to remove an existing integration from a project after confirming the integration id. this action cannot be undone and requires organization administrator or project owner permissions.
Connect any two apps with Notis in the middle.
Jira and Bugsnag, 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 Bugsnag.