Skip to content
Notis

Auto-Resolve Jira Tickets from Google Docs Approvals

A comment saying 'Approved' closes the ticket. Reduce friction between review and closure.

Trigger

Comment Added (Docs/Sheets/Slides)

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

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

Reviews happen in Google Docs, but closing work in Jira happens separately. Tickets stay open long after approval, creating false busy-ness.

  • Tickets close automatically when approved in Docs
  • Faster workflow completion without manual closing
  • Clear audit trail of approvals
  • Reduce stale tickets in Jira
  • Faster throughput from review to done

Setup

Build it in a few focused steps.

  • 1Connect Google Drive and Jira to Notis.
  • 2Create an automation: 'When someone adds a comment to my Google Docs containing words like Approved, Done, or Looks Good, transition the corresponding Jira ticket to Resolved.'
  • 3Notis learns to detect approval keywords. Customize which words trigger closure.
  • 4Test by adding an approval comment to a Google Doc and watching the Jira ticket transition to Done.

Questions about this workflow

What words trigger closure? Can I customize them?

Common approvals like 'Approved', 'LGTM', 'Looks good', 'Done' work by default. You can add more or remove some to fit your team's language.

What if someone says 'Approved with changes'?

You can configure Notis to treat 'with changes' as conditional approval, moving the ticket to 'In Review' instead of 'Done.'

Can I add a comment to the Jira ticket when it closes?

Yes. For example: 'Approved on [date] in [Doc name]' gets added to the ticket automatically.

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 triggers

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