Skip to content
Notis

Keep a Jira deployment comment current

Refresh a known deployment comment with newer Buildkite context, so the issue has one current summary to consult.

Trigger

Recurring schedule

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

Action

Update Comment

Updates text content or visibility of an existing jira comment.

Why this helps

Repeated deployment updates create scattered comments, making it harder to find the latest release summary.

  • Keep a designated comment current as deployment details change.
  • Reduce repeated comment clutter on the issue.
  • Maintain a concise deployment summary in Jira.

Setup

Build it in a few focused steps.

  • 1Connect Buildkite and Jira once in Notis and make current deployment context available to the scheduled run.
  • 2Create an automation and specify the issue key and existing comment ID to update.
  • 3Describe which details should be refreshed and which content should remain in the comment.
  • 4Choose a recurring schedule and report destination.
  • 5Test with one real issue and comment, then verify the updated text.

Questions about this workflow

How does the workflow find the comment to update?

Provide the Jira issue key and existing comment ID, or a reliable way for Notis to retrieve them. It should not guess which comment to replace.

Will the scheduled run retrieve Buildkite data automatically?

Only if the data is available through a connected source or supplied context. Provide that source and have the automation report if it cannot retrieve current details.

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.