Prerequisite: Third-party connectors are available only on the Sana Enterprise tier, with one exception: the Workday connector is included for both Sana Core and Sana Enterprise.

Introduction

Connect Jira to Sana to search and manage issues. Track work, transition issues, assign issues, and stay on top of your team's progress with context from your connected apps.

In summary, the connector has the following key characteristics:

Category: Project management
Connector type: Real-time
Auth type: OAuth
Hosting type: Managed

Capabilities

This connector is able to do the following:

Capability

List users

List spaces

Find issues

List comments

Create comments

Update comments

Manage boards

Manage sprints

List epics

Tools

While the capabilities above describe what the connector can do at a high level, the underlying tools show exactly which operations the agent can use when you ask Sana about Jira. In practice, the agent may call one or more tools to achieve a single capability.

Tool

Add comment to issue

Add watcher to issue

Assign issue

Check issues against jql

Count issues using jql

Create custom field options context

Create future sprint

Create version

Delete project

Get all projects

Get board

Get cloud id

Get current user

Get issue

Get issue picker suggestions

Get issue types

Get sprint

Get task

Get transitions

Get user

Get users

List board issues

List boards

List epic issues

List epics

List issue comments

List labels options

List sprint issues

List sprints

Move issues to sprint

Search issues with jql

Search issues with jql post

Transition issue

Update comment

Note: This article lists the connector's full set of tools. Your workspace owner can disable individual tools for your workspace, so some of those listed here may not be available to your agents. If a tool you expected is missing, reach out to your workspace owner.

Triggers

While tools are the actions an agent takes on your behalf, triggers are the events that can start an agent automatically. When you build an agent, you can choose one of the triggers below as its starting point. For example, having the agent run every time something new happens in Jira.

Trigger

New Event

New Issue Created Event (Instant)

New Issue Deleted Event (Instant)

New Issue Updated Event (Instant)

Scope and permissions

This connector uses OAuth. When you connect your account, you will need to sign into your account and grant the required permissions:

Scope	Purpose
read:jira-work	Read Jira work data like spaces and issues
manage:jira-project	Create and configure projects, roles, and settings
read:jira-user	Read Jira user profiles and basic account details
write:jira-work	Create, edit, transition, and comment on issues
read:me	Read information about the currently authenticated user
offline_access	Refresh access tokens when the user is offline
read:issue-details:jira	Read detailed issue content, history, and comments
read:field:jira	Read field definitions, metadata, and field values
read:project:jira	Read project metadata, categories, and configurations
write:field.option:jira	Create and update options for custom select fields
read:custom-field-contextual-configuration:jira	Read context-specific custom field configs per project
read:jql:jira	Validate and inspect JQL queries and search metadata
manage:jira-webhook	Create, update, and delete Jira webhooks for events

Set up instructions

Prerequisites:

You are a Sana Enterprise user – all third-party connectors except the Workday connector are available only for users on the Sana Enterprise tier.
Your Sana workspace owner has enabled this connector – if the workspace owner has disabled the connector it won't appear in the list of available connectors.

Step 1: Go to the connectors page in Sana

In Sana, click on your profile icon and name in the bottom left corner and select Connectors.

Step 2: Find Jira in the list of available connectors

Scroll to the Available connectors section and locate Jira.

Note: If you can't find a connector in this list, it means one of the following:

You've already connected it — check the ”Active connectors” section at the top of the connectors page, or
Your workspace owner has disabled this connector for your workspace — reach out to them for more information or to request that it be enabled.

Step 3: Hover the connector card and click the connect button

Hover the Jira card and click the Connect button.

Tip: If you click the card itself instead of the Connect button, you'll open a connector detail page with more information about its capabilities.

Step 4: Initialize the Pipedream connection

When clicking Connect in the previous step, a pop-up will appear powered by Pipedream. Click the Continue button in the pop-up to initialize the set up.

Note: Sana uses Pipedream to connect your account. Pipedream is a Workday product, trusted by millions of people to keep their data secure.

Step 5: Sign in to Jira and approve the requested scopes

You'll be redirected to Jira to go through their OAuth flow. Sign in and approve the scopes Sana needs to operate the connector.

Step 6: Complete the set up

You've successfully connected your Jira account. Click Continue to complete the setup and start using the connector.

Known limitations

Attachments: The connector cannot read or write attachments in Jira.
Managed Jira only: The connector only supports managed (cloud) Jira — self-hosted instances are not supported.
Deletion: The connector cannot delete users, issues, or comments.
Custom objects and fields: Limited support for writing and updating custom objects and fields.

Frequently asked questions

Q: Which Jira sites can Sana access?

A: When you connect Jira, you choose a single site to give Sana access to. Access is cumulative: if you connect again and choose a different site, it's added to the ones before rather than replacing them, so over time one connection can cover several sites. Sana can only access sites you've connected — it can't reach sites you haven't.

Q: How do I remove Sana's access to Jira?

A: Disconnect Jira on the Connectors page in Sana; this stops Sana from accessing your Jira. To also remove the authorization from your Atlassian account, open your connected apps at id.atlassian.com/manage-profile/apps and remove access for the app. Because sites are granted together, this removes access to all connected sites at once — it isn't possible to remove a single site while keeping the others.