Automatically Assign Jira Tickets from Google Drive Shares
Sharing a file now assigns work. Ownership is explicit, no follow-up conversations required.
Trigger
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.
Action
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Why this helps
Sharing a Google Drive file with a teammate doesn't automatically assign ownership in Jira, leading to unclear work handoffs and responsibility gaps.
- Automatic work ownership when files are shared
- Clear responsibility without Slack pings
- Reduce misunderstandings about who owns what
- Faster handoffs between team members
- Cleaner Jira board with accurate assignments
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Jira to Notis.
- 2Create an automation: 'When a file is shared in Google Drive with someone, assign the matching Jira ticket to that person.'
- 3Notis will ask: 'How do you want me to match files to tickets?' (by name, folder, or keyword). Define that matching rule.
- 4Test by sharing a Google Drive file with a teammate and checking if the corresponding Jira ticket was assigned to them.
Questions about this workflow
What if the file doesn't have a corresponding Jira ticket?
You can configure Notis to either skip it, or automatically create a new ticket first. Your choice.
Can I assign to multiple people if I share a file with multiple teammates?
Yes. Notis will identify all recipients and assign the ticket to each person if you set that up, or flag it for manual review.
What if someone is shared a file but already has an open assignment on that ticket?
Notis can check existing assignments first. If the ticket is already owned, it can add the new person as a watcher or collaborator instead.
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.
Add Attachment
Uploads and attaches a file to a jira issue.
File Created
Triggers when a new file is created in Google Drive.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
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.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
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``.
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 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.