Automatic Weekly Sprint Review from Jira

No Friday report writing. Notis searches Jira, compiles your weekly progress, and sends it to Slack.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

Jira logo

Action

Search Issues Using JQL (GET)

Searches for jira issues using jql with pagination and field selection.

Why this helps

Writing a weekly sprint review requires digging through Jira, counting closed tickets, and summarizing progress. It's repetitive work that delays Friday handoffs.

  • Automatic weekly progress reports
  • Faster sprint reviews without manual digging
  • Consistent metrics and transparency
  • Reduce Friday overhead
  • Clear visibility into team velocity

Setup

Build it in a few focused steps.

  • 1Connect Notis and Jira.
  • 2Create a scheduled automation: 'Every Friday at 5 PM, search Jira for all issues closed this week and all in-progress tickets, then summarize the results and send a report.'
  • 3Tell Notis which projects to include and what format you want (email, Slack message, etc.).
  • 4Run once manually to review the report format, then set it to run on schedule.

Questions about this workflow

Can I customize which fields are included in the report?

Yes. For example: 'Include the ticket title, assignee, and hours logged' or 'Just show closed vs. in-progress counts.'

What if we don't close many tickets some weeks?

Notis will report what actually happened. You can ask it to flag slow weeks or highlight blocked tickets instead.

Can I send this report to multiple channels or people?

Absolutely. You can send it to Slack, email specific teammates, or post it to a shared doc.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Google Drive logo

Google Drive triggers

Jira logo

Jira actions

Comment Added (Docs/Sheets/Slides)

Triggers when a new comment is added to Google Docs, Sheets, or Slides.

TriggerPolling

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

File Created

Triggers when a new file is created in Google Drive.

TriggerPolling

Add Comment

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

ActionInstant

File Deleted or Trashed

Triggers when a file is moved to trash or permanently deleted in Drive.

TriggerPolling

Add Watcher to Issue

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

ActionInstant

File Shared (Permissions Added)

Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.

TriggerPolling

Assign Issue

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

ActionInstant

File Updated

Triggers when a file's metadata or content changes in Google Drive.

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

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

Create Issue

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

ActionInstant

New File Matching Query

Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.

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 Drive 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.