Auto-move Jira issues to sprint based on calendar sync

Your sprints should reflect your actual calendar commitments. When Notis syncs a recurring calendar event, it moves the related issue into your active sprint so the team knows it's happening now.

Trigger

Calendar Event Sync

Polling trigger that returns full event data including details, attendees, and metadata. For real-time notifications with basic info, use Calendar Event Changes (webhook).

Jira logo

Action

Move Issues to Sprint

Moves one or more jira issues to a specified active sprint.

Why this helps

You have recurring work blocks on your calendar, but the related Jira issues linger in the backlog, making it look like the sprint is understaffed when it's actually full.

  • Sprint board accurately reflects your time-blocked calendar commitments
  • No manual sprint planning for recurring work blocks
  • Team velocity and capacity planning align with actual calendar availability

Setup

Build it in a few focused steps.

  • 1Connect Google Calendar and Jira to Notis.
  • 2Create an automation: "When a recurring calendar event syncs, move its related Jira issue to the active sprint."
  • 3Specify which calendar or recurring event patterns trigger this (e.g., weekly standup, sprint planning, etc.).
  • 4Test by triggering a calendar sync and verifying the issue moves to the active sprint.
  • 5Optionally adjust: only move issues if they're in To Do status, to avoid re-triggering for already-in-progress work.

Questions about this workflow

What if there's no active sprint?

Notis will note this in the run report. You can refine the automation to create a sprint automatically if none exists, or to fail gracefully.

Can I move issues to different sprints based on the event?

Yes. If you have named sprints (Sprint 1, Sprint 2, etc.), Notis can match calendar events to sprints by name or date.

What about one-off calendar events vs. recurring?

This automation focuses on recurring calendar events, which typically represent ongoing sprint work. One-offs can use a different automation.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Google Calendar to Jira. A trigger fires from one place; an action lands in another.

Google Calendar logo

Google Calendar triggers

Jira logo

Jira actions

Attendee Response Changed

Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status.

TriggerPolling

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Event Canceled or Deleted

Triggers when a Google Calendar event is cancelled or deleted. Returns minimal data: event_id, summary (if available), and cancellation timestamp.

TriggerPolling

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

Event Starting Soon

Triggers when a calendar event is within a configured number of minutes from starting. Returns event details, time remaining, attendees, and join links when available.

TriggerPolling

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Calendar Event Changes

**SOON TO BE DEPRECATED** - Use Calendar Event Sync (polling trigger) instead. Real-time webhook trigger for calendar event changes. Returns event metadata only. For full event data, use Calendar Event Sync (polling trigger).

TriggerInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

Event Created

Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info.

TriggerPolling

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

Calendar Event Sync

Polling trigger that returns full event data including details, attendees, and metadata. For real-time notifications with basic info, use Calendar Event Changes (webhook).

TriggerPolling

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

Event Updated

Triggers when an existing Google Calendar event is modified. Returns the event ID, change type, and the specific fields that changed with their previous and new values.

TriggerPolling

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

Connect any two apps with Notis in the middle.

Not just Google Calendar and Jira. Any combination from 985+ 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.