Update Jira after a Buildkite deployment
Pass a deployment result to Notis and update the related Jira issue with the outcome and build link.
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
Deployment outcomes live in Buildkite while Jira tickets remain stale, so teams spend time checking both tools.
- Keep deployment context alongside the tracked Jira work.
- Reduce manual status note updates after a build.
- Include the build or deployment link when supplied.
Setup
Build it in a few focused steps.
- 1Connect Buildkite and Jira once in Notis.
- 2Create an automation and describe how deployment results should update Jira.
- 3Include a reliable Jira issue identifier and deployment result in the webhook data.
- 4Choose a webhook trigger and a run-report destination.
- 5Test with one real deployment result and verify the intended issue fields were updated.
Questions about this workflow
Can this change a Jira workflow status?
This workflow uses Edit Issue, which updates issue fields. To transition workflow status, a separate transition action would be needed.
What if the webhook does not include the Jira issue key?
Supply an issue key or another reliable association in the request. Without one, Notis should report that it cannot safely identify the issue to update.
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.