Review compliance when a Jira issue changes
A status or assignee change can signal that compliance follow-up needs attention. Ask Notis to retrieve the relevant 21risk compliance data and summarize what it shows.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Get Compliance
Tool to retrieve compliance data for sites, categories, or questions. use when you need odata-based compliance data for analytics or reporting.
Why this helps
Important changes can get buried in Jira activity while compliance checks sit elsewhere, leaving founders to remember what needs a second look.
- Trigger a compliance data review from an existing Jira issue change.
- Summarize relevant site, category, or question data from 21risk.
- Make unmatched or insufficient issue details visible for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Jira and 21risk once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to retrieve relevant 21risk compliance data for each changed Jira issue and summarize the results, calling out any details needed to identify the site or question.
- 4Pick the Jira Updated Issue trigger and choose where run reports should go.
- 5Test with one real issue update and review the report.
Questions about this workflow
Will this trigger for Jira comments?
No. The Jira Updated Issue event covers changes to an issue, but comment activity does not fire this trigger.
Can Notis tell whether compliance got better or worse?
Only if the returned data supports that comparison or you provide a baseline. Otherwise, the report can summarize current data and identify what's missing for comparison.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to 21risk. A trigger fires from one place; an action lands in another.
Jira triggers
21risk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Compliance
Tool to retrieve compliance data for sites, categories, or questions. use when you need odata-based compliance data for analytics or reporting.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Items (BETA)
Tool to retrieve items (beta) from the 21risk odata api. use when you need a filtered and paged list of items for analytics and reporting. example: get items($filter="item cost gt 100", $top=50).
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Get Items Per Month
Tool to retrieve fact table data for itemspermonth, one row per question per site per month. use when querying monthly item data with odata parameters ($filter, $top, $skip, $select, maxpagesizeinmb).
New Project
Triggered when a new project is added in Jira
Get Organizations
Tool to retrieve organizations from the 21risk odata api. use when you need to list, filter, or paginate organizations via odata parameters after authentication is confirmed.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Get Properties
Tool to fetch a list of properties related to sites, including cope information and other relevant data. use when you need property insurance details via odata api after authentication.
Get Reports
Tool to retrieve audit reports, including draft, published, and scheduled reports. use when you need a paginated list of reports with optional odata filtering.
Get RiskModel Categories
Tool to retrieve risk model categories for grouping questions and compliance checks. use when you need to filter, select, or paginate risk model categories via odata parameters ($filter, $select, $orderby, $top, $skip, $count).
Get Risk Models
Tool to retrieve risk models used for audits and compliance. use when you need to list available risk models with optional odata queries.
Connect any two apps with Notis in the middle.
Jira and 21risk, 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 21risk.