Skip to content
Notis

Create Jira versions for planned Buildkite releases

Keep Jira release planning in step with upcoming Buildkite releases using the project and version details you provide.

Trigger

Recurring schedule

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

Action

Create Version

Creates a new version for releases or milestones in a jira project.

Why this helps

Release milestones are planned in one place but missing from Jira, creating avoidable setup and tracking work.

  • Create a Jira version from available release planning details.
  • Check for an existing version before creating another.
  • Keep release dates and descriptions alongside Jira project work when supplied.

Setup

Build it in a few focused steps.

  • 1Connect Buildkite and Jira once in Notis and make planned release data available to the scheduled run.
  • 2Create an automation and describe which planned releases should become Jira versions.
  • 3Specify the Jira project and release details in your instruction or data source.
  • 4Choose a recurring schedule and where run reports should go.
  • 5Test with one real planned release and verify the project and version details.

Questions about this workflow

Does the schedule retrieve Buildkite release plans by itself?

No. Provide a connected source or user-supplied release data that Notis can access. The schedule only starts the run.

Will this avoid duplicate versions?

Instruct Notis to check the project's existing versions before creating a new one. It can only compare against data it can retrieve.

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.