Move ready call follow-ups to their next Jira state
Use the call history available to Notis and a clear readiness rule to move matching follow-up issues along 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
Follow-up issues can remain in an old Jira state after the call has already changed what should happen next.
- Keep Jira workflow states closer to the call information available to the team.
- Apply a consistent, user-defined readiness rule.
- Reduce manual status checks across call history and Jira.
Setup
Build it in a few focused steps.
- 1Connect Callingly and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for follow-up transitions.
- 3Tell Notis which call information and Jira issue criteria mean a follow-up is ready to transition, and which available Jira transition should be used.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real call and issue, and confirm the intended transition is available.
Questions about this workflow
Can this transition any Jira issue?
Only issues identified by your instruction and accessible to the connected Jira user can be transitioned. Jira must also offer the requested transition for the issue.
Where does the readiness rule come from?
You define it using information available in Callingly call history and the Jira issue. Notis cannot infer a business rule or data that is not provided.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Callingly to Jira. A trigger fires from one place; an action lands in another.
Callingly 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.
Callingly 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.