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 your self-hosted Jira Data Center instance to Sana to manage boards, sprints, and epics, and move issues between sprints and the backlog without leaving your chat.
In summary, the connector has the following key characteristics:
Category: Project management
Connector type: Real-time
Auth type: API keys
Hosting type: Managed
Capabilities
This connector is able to do the following:
Capability |
List boards |
Update sprints |
List epics |
List issues |
Move issues |
List worklogs |
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 Data Center. In practice, the agent may call one or more tools to achieve a single capability.
Tool |
Create board |
Create filter |
Create future sprint |
Delete sprint |
Get board |
Get issues from backlog |
Get resolution |
Get server info |
Get sprint |
Get updated work logs |
Get worklogs by id |
List board issues |
List boards |
List epic issues |
List epics |
List filter id options |
List issues without epic |
List project id options |
List resolutions |
List sprint issues |
List sprints |
List worklog ids actions |
Move issues to backlog |
Move issues to sprint |
Update sprint fully |
Update sprint partially |
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.
Scope and permissions
This connector uses API keys. When you connect your account, we securely store your keys to connect to this connector's APIs. The scopes for this connector depends on the scopes you assign your API key in Jira Data Center when generating the key.
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 Data Center in the list of available connectors
Scroll to the Available connectors section and locate Jira Data Center.
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 Data Center 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: Provide your Jira Data Center credentials
You'll be asked to paste the credentials for Jira Data Center so Sana can store them securely and use them to call the connector's APIs on your behalf.
Step 6: Complete the set up
You've successfully connected your Jira Data Center account. Click Continue to complete the setup and start using the connector.
Known limitations
Issues: The connector works with issues only through boards, sprints, and epics — it can list the issues in a board, sprint, epic, or backlog, but cannot look up or search for an individual issue by key (e.g. PROJ-123), and cannot create, transition, or comment on issues.
Network access: Sana connects to your Jira Data Center API URL from Sana's cloud connector platform — being reachable over the public internet is not enough if a firewall filters traffic. Corporate firewalls must allow traffic from the connector platform (contact support for the IP ranges to allowlist), otherwise requests time out.



