Transition Jira issues after a confirmed release
When Buildkite reports a confirmed release, transition its related Jira issue using an available workflow transition.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Transition Issue
Transitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.
Why this helps
A completed release can leave its Jira issue in an outdated state until someone remembers to update it.
- Keep Jira workflow state aligned with confirmed release follow-up.
- Reduce manual ticket updates after a release.
- Use Jira's available transitions rather than assuming a status change is allowed.
Setup
Build it in a few focused steps.
- 1Connect Buildkite and Jira once in Notis.
- 2Create an automation and specify which confirmed outcome should cause a transition.
- 3Include the Jira issue key and desired transition name in the webhook context or instruction.
- 4Choose a webhook trigger and where run reports should go.
- 5Test with one real release issue and verify the resulting Jira status.
Questions about this workflow
Will any requested status always be available?
No. Jira exposes transitions available for an issue's current state. If the requested transition is unavailable, the run should report that result.
Can this run for an unsuccessful deployment?
Only if you explicitly define that behavior. For this workflow, use a confirmed release outcome and specify the transition that should follow it.
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.