Catch unresolved Buildkite failures with Jira follow-up
Use a scheduled review to turn unresolved failures in available Buildkite data into clear Jira follow-up.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Why this helps
A failed build can disappear from attention when no one creates a durable follow-up or checks whether it was resolved.
- Surface unresolved failures for durable tracking.
- Create issues only for items the available history identifies as unresolved.
- Make missing history or resolution data visible in the report.
Setup
Build it in a few focused steps.
- 1Connect Buildkite and Jira once in Notis and make failure and resolution history available.
- 2Create an automation and define what qualifies as unresolved using available data.
- 3Ask Notis to create one Jira issue per distinct unresolved failure and include its build reference.
- 4Choose a recurring schedule and run-report destination.
- 5Test with one real failure record and confirm the issue is appropriate.
Questions about this workflow
How does Notis know a failure is unresolved?
Provide failure history and a clear resolution signal or rule. Without resolution data, Notis cannot reliably determine whether an item remains unresolved.
Will this create duplicate Jira issues?
Tell Notis to search existing Jira issues using a reliable build or failure identifier before creating a new one. If no identifier is available, duplicates cannot be ruled out reliably.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Buildkite to Jira. A trigger fires from one place; an action lands in another.
Buildkite triggers
Jira actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Buildkite 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.