Spot Blockages: Weekly Transition Availability Check
Every Friday, before your retro, this workflow checks which Jira issues are stuck or can't transition smoothly. You'll get a report of blockers and workflow friction so you can address them before they cascade.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Transitions
Retrieves available workflow transitions for a jira issue.
Why this helps
Issues pile up in certain statuses because of workflow blockers or missing prerequisites. You don't notice until work is significantly delayed.
- Spot workflow friction early before it slows the entire team
- Get a report of issues stuck at specific transitions
- Use insights to improve your Jira workflow design
- Plan retros around actual workflow data, not just feelings
Setup
Build it in a few focused steps.
- 1Connect Jira to your Notis workspace.
- 2Create an automation: ask Notis or use New Automation > Cron.
- 3Set the trigger to 'Recurring Schedule' for Friday 4pm (before retro).
- 4Write your prompt: 'Every Friday, check all issues in progress and report which ones have limited transition options or are blocked. Highlight issues that have been in the same status for more than 3 days.'
- 5Choose your notification channel and save. You'll get a weekly report every Friday.
Questions about this workflow
What does 'limited transition options' mean?
Notis checks the available workflow transitions for each issue. If an issue can only move to one status or is blocked from key transitions, it gets flagged.
Can I track specific workflows or projects?
Yes. Your prompt can say: 'Only check issues in the Backend project' or 'Only track issues with the Release label.' Notis focuses on what matters.
How actionable is this for my team?
Very. The report tells you exactly which issues are stuck and why. You can bring the list to retro and decide if the workflow needs adjustment or if issues need manual intervention.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Hubspot to Jira. A trigger fires from one place; an action lands in another.
Hubspot triggers
Jira actions
Contact Created Trigger
Contact Created Trigger
Add Attachment
Uploads and attaches a file to a jira issue.
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
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.
Not just Hubspot and Jira. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Jira.