Keep Databricks app access requests moving from Jira
Apply a specified app permission change from an updated Jira issue without replacing the app's full permission set.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Update Databricks App Permissions
Tool to incrementally update permissions for a Databricks app. Use when you need to modify specific permissions without replacing the entire permission set. This PATCH operation updates only the specified permissions, preserving existing permissions not included in the request. For replacing all permissions, use SetPermissions instead.
Why this helps
App access requests can remain unresolved when teams have to translate Jira approvals into manual permission changes.
- Apply specified permission changes while preserving permissions not included in the request.
- Keep the Jira request as the reference for the change.
- Reduce manual app access administration.
Setup
Build it in a few focused steps.
- 1Connect Jira and Databricks once in the Notis portal.
- 2Create an automation and describe how to apply approved app permission changes.
- 3Pick Jira Updated Issue as the trigger.
- 4Choose where Notis should send run reports.
- 5Test with one real Jira issue that clearly names the app, principals, permission levels, and approval.
Questions about this workflow
Does this replace every existing app permission?
No. This action incrementally updates specified permissions and preserves permissions that are not included.
Which details should the Jira issue contain?
It should clearly identify the Databricks app, the principals, the permission levels, and approval for the change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Databricks. A trigger fires from one place; an action lands in another.
Jira triggers
Databricks actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Member to Security Group
Tool to add a user or group as a member to a Databricks security group. Use when you need to grant group membership for access control.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Custom LLM Agent
Tool to delete a Custom LLM agent created through Agent Bricks. Use when you need to remove a custom LLM and all associated data. This operation is irreversible and deletes all data including temporary transformations, model checkpoints, and internal metadata.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create Databricks App
Tool to create a new Databricks app with specified configuration. Use when you need to create apps hosted on Databricks serverless platform to deploy secure data and AI applications. The app name must be unique within the workspace, contain only lowercase alphanumeric characters and hyphens, and cannot be changed after creation.
New Project
Triggered when a new project is added in Jira
Delete Databricks App
Tool to delete a Databricks app from the workspace. Use when you need to remove an app and its associated service principal. When an app is deleted, Databricks automatically deletes the provisioned service principal.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Deploy Databricks App
Tool to create a deployment for a Databricks app. Use when you need to deploy an app with source code from a workspace path. The deployment process provisions compute resources and uploads the source code. Deployments can be in states: IN_PROGRESS, SUCCEEDED, FAILED, or CANCELLED.
Get Databricks App Details
Tool to retrieve details about a specific Databricks app by name. Use when you need to get comprehensive information about an app including configuration, deployment status, compute resources, and metadata.
Get Databricks App Permission Levels
Tool to retrieve available permission levels for a Databricks app. Use when you need to understand what permission levels can be assigned to users or groups for a specific app. Returns permission levels like CAN_USE and CAN_MANAGE with their descriptions.
Get Databricks App Permissions
Tool to retrieve permissions for a Databricks app. Use when you need to check who has access to an app and their permission levels. Returns the access control list including inherited permissions from parent or root objects.
Connect any two apps with Notis in the middle.
Jira and Databricks, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Databricks.