Skip to content
Notis

Move Jira issues after Botbaba resolution updates

Keep issue status aligned with a meaningful resolution update, while leaving workflow history in Jira.

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

When a problem is resolved in a conversation, the Jira issue can remain in an outdated status until someone remembers to update it.

  • Reflect a confirmed resolution in the Jira workflow.
  • Reduce stale issue statuses after customer conversations.
  • Keep the transition recorded in Jira.

Setup

Build it in a few focused steps.

  • 1Connect Botbaba and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3In one instruction, tell Notis to transition the identified issue only when the incoming Botbaba update clearly confirms the specified resolution state.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one resolved example and verify the Jira issue moved to the intended status.

Questions about this workflow

Will every Botbaba update transition an issue?

The instruction should limit transitions to updates that clearly meet your stated resolution condition. A test helps confirm that behavior.

What if the transition is not available for the issue?

Jira workflow transitions vary by issue and status. The automation can only use a transition available for that issue.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Botbaba 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.

Botbaba 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.