Skip to content
Notis

Keep Jira follow-ups aligned with scorecard results

Submit a KPI result with the Jira issue reference. Notis can update the existing follow-up when the new result changes its context or next step.

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

Jira tickets can keep outdated assumptions after a scorecard result changes.

  • Keep an existing Jira issue aligned with a new result.
  • Preserve changes in KPI status and supplied context.
  • Avoid unnecessary edits when the update does not affect the ticket.

Setup

Build it in a few focused steps.

  • 1Connect BSC Designer and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it.
  • 3In one instruction, ask Notis to use the supplied Jira issue key and update that issue only when the submitted KPI result changes its context or next step.
  • 4Choose the Notis webhook trigger and select where run reports go.
  • 5Test with one real KPI update and its existing Jira issue key.

Questions about this workflow

How does Notis know which Jira issue to update?

Include the issue key in the webhook request or in the information supplied to Notis. The BSC Designer trigger list provided here contains no event payload or issue link.

Will every result overwrite the Jira description?

Your instruction should specify which meaningful changes merit an edit and what context to preserve. Test with one issue before relying on the workflow.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link BSC Designer to Jira. A trigger fires from one place; an action lands in another.

BSC Designer 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.

BSC Designer 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.