Automatically Link Jira Issues from Google Drive Files
Drive query results automatically link related Jira issues. Traceability without manual linking.
Trigger
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``.
Action
Link Issues
Links two jira issues using a specified link type with optional comment.
Why this helps
Related tickets stay siloed in Jira while their supporting documents live separately in Drive, making traceability hard and relationships invisible.
- Automatic issue linking from Drive files
- Clear traceability across issues
- Reduce manual link creation
- Better visibility into issue relationships
- Faster dependency identification
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Jira to Notis.
- 2Create an automation: 'When files matching my query [e.g., Bug Reports] are found in Google Drive, link the corresponding Jira issues together as related or dependent.'
- 3Tell Notis the link type (related, blocked by, depends on, etc.) and which issues to link.
- 4Test by creating or finding matching files in Google Drive and verifying Jira issues are linked.
Questions about this workflow
What if multiple Jira issues match a single Drive file?
Notis will link all of them as related. You can specify the link type (depends on, related to, blocked by, etc.).
Can I run this query manually or only on a schedule?
Both. This trigger runs when matching files appear. You can also manually trigger it to backlink existing files.
How does Notis know which issues to link? By file name?
By file name, keywords, or metadata. You describe how in your plain-language instruction, and Notis learns the pattern.
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 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.