Move resolved transaction investigations forward in Jira
When a webhook confirms the status you care about, have Notis transition the related Jira issue using an available workflow transition.
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
Resolved transaction work can remain in an active Jira state if someone has to notice and move it manually.
- Keep Jira workflow state aligned with supplied transaction status.
- Reduce manual ticket maintenance after a resolution.
- Apply your own definition of a resolved transaction.
Setup
Build it in a few focused steps.
- 1Connect Blocknative and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for resolved transaction handling.
- 3Tell Notis which supplied transaction statuses qualify and which Jira transition to use for the related issue.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real status report and verify the available transition and resulting Jira state.
Questions about this workflow
Can every Jira issue use the same transition?
No. Available transitions depend on the issue's workflow state. Make sure your instruction accounts for the transitions available on the relevant issues.
What if the webhook does not identify a Jira issue?
Notis needs an unambiguous Jira issue key or a reliable way to find the issue from available context. Without it, the intended issue cannot be transitioned safely.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blocknative to Jira. A trigger fires from one place; an action lands in another.
Blocknative 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.
Blocknative 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.