Move Jira issues forward after Botpress confirmation
When a Botpress conversation confirms a fix or handoff, let Notis check for the referenced issue and move it forward in Jira.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
A user confirmation can sit in chat while the corresponding Jira ticket stays in an outdated workflow state.
- Reflect clear user confirmations in Jira workflow progress.
- Reduce manual status updates after a resolved exchange.
- Keep the transition tied to explicit conversation evidence.
Setup
Build it in a few focused steps.
- 1Connect Botpress and Jira once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3In one instruction, ask Notis to find explicit confirmations in available Botpress history and transition the referenced Jira issue only when the intended next state is clear.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real confirmation and verify the available transition for its Jira issue.
Questions about this workflow
Can Notis use any Jira status as the next state?
The transition action uses transitions available in the Jira issue workflow. Ask Notis to proceed only when the intended transition is available and clear.
What counts as confirmation?
Define the exact evidence in your instruction, such as a user explicitly confirming the reported issue is resolved.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botpress to Jira. A trigger fires from one place; an action lands in another.
Botpress triggers
Jira actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Botpress 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.