Skip to content
Notis

Find Jira issues that need deployment follow-up

Use a recurring Jira search to surface deployment follow-up issues and review them without digging through boards.

Trigger

Recurring schedule

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

Action

Search Issues Using JQL (GET)

Searches for jira issues using jql with pagination and field selection.

Why this helps

Deployment follow-up tickets can stay open and easy to miss among unrelated Jira work.

  • Surface matching follow-up issues on a predictable schedule.
  • Use a JQL query that reflects the team's actual Jira labels or fields.
  • Review results in the run report without creating duplicate work.

Setup

Build it in a few focused steps.

  • 1Connect Jira once in Notis and make the relevant Buildkite deployment context available if needed.
  • 2Create an automation and provide a JQL query for the deployment follow-up issues you want to find.
  • 3Ask Notis to summarize the matching issues and flag items needing attention.
  • 4Choose a recurring schedule and where reports should go.
  • 5Test with one real Jira search and confirm the results match your intended criteria.

Questions about this workflow

Does this create or update Jira issues?

No. This workflow searches Jira and presents the results in its run report. It does not change issues.

Does Jira know which issues came from Buildkite?

Only if your Jira issues contain a searchable marker or field, such as a label or text your team already uses. Provide the appropriate JQL; the workflow does not assume an undocumented field.

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.

TriggerScheduled

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

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.