Keep Jira Event Status Details Aligned
Use a recurring check to keep identified event issues current when the status information is available to Notis.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Edit Issue
Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.
Why this helps
Jira can show stale event details when updates happen elsewhere and nobody remembers to refresh the issue.
- Refresh identified Jira issue details during a recurring review.
- Reduce stale context for event coordination.
- Make a consistent check part of the team's routine.
Setup
Build it in a few focused steps.
- 1Connect ChMeetings and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis in plain language from any channel.
- 3Describe the outcome: review available event status details and update only the identified Jira issue fields your team wants kept current.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real event issue and verify the updated details.
Questions about this workflow
Can this workflow change Jira workflow status?
It edits issue fields. To move an issue through a Jira workflow, use a transition action and specify a valid available transition.
What if event status information is unavailable to Notis?
Supply the missing status information in accessible data or the automation context. Notis cannot reconcile data it cannot retrieve.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Chmeetings to Jira. A trigger fires from one place; an action lands in another.
Chmeetings 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.
Chmeetings 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.