Use Jira updates to prompt a document follow-up check
A changed assignee or status can be a good moment to review document progress. Notis can bring the Boloforms list into the run report.
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 Documents List
Tool to retrieve a list of documents associated with the account. use when you need to list all documents.
Why this helps
A handoff or status change in Jira can leave signature follow-up dependent on someone remembering to check another app.
- Prompt a document review when Jira work changes.
- Make follow-up easier to notice during handoffs.
- Keep a run report with the retrieved document list.
Setup
Build it in a few focused steps.
- 1Connect Jira and Boloforms once in the Notis portal.
- 2Create an automation by telling Notis to retrieve Boloforms documents after a Jira issue update and summarize items that may need follow-up.
- 3Pick the Jira Updated Issue trigger for the project you configure.
- 4Choose where Notis should send run reports.
- 5Test with one real issue update and check whether the report gives you a useful next step.
Questions about this workflow
What counts as an issue update?
Changes to an existing issue, such as its status, assignee, or another issue field. Comment activity does not trigger this event.
Does this send reminders or update Boloforms?
No. The listed Boloforms action only retrieves the account's document list. Notis can summarize it in the run report, but this action does not send reminders or change documents.
Can this run when a Jira comment is added?
No. The Updated Issue event does not fire on comment activity.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Boloforms. A trigger fires from one place; an action lands in another.
Jira triggers
Boloforms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Documents List
Tool to retrieve a list of documents associated with the account. use when you need to list all documents.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
New Project
Triggered when a new project is added in Jira
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.
Connect any two apps with Notis in the middle.
Jira and Boloforms, 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 Boloforms.