Jira Data Center
Overview
Pre-built tooling
✅ Authorization
| Tools | Status |
|---|---|
| Pre-built authorization (OAuth) | ✅ |
| Credentials auto-refresh | ✅ |
| Auth parameters validation | ✅ |
| Pre-built authorization UI | ✅ |
| Custom authorization UI | ✅ |
| Expired credentials detection | ✅ |
✅ Read & write data
| Tools | Status |
|---|---|
| Pre-built integrations | 🚫 (time to contribute: <48h) |
| API unification | ✅ |
| 2-way sync | ✅ |
| Webhooks from Tenklo on data modifications | ✅ |
| Real-time webhooks from 3rd-party API | 🚫 (time to contribute: <48h) |
| Proxy requests | ✅ |
✅ Observability & data quality
| Tools | Status |
|---|---|
| HTTP request logging | ✅ |
| End-to-end type safety | ✅ |
| Data runtime validation | ✅ |
| OpenTelemetry export | ✅ |
| Slack alerts on errors | ✅ |
| Integration status API | ✅ |
✅ Customization
| Tools | Status |
|---|---|
| Create or customize use-cases | ✅ |
| Pre-configured pagination | 🚫 (time to contribute: <48h) |
| Pre-configured rate-limit handling | 🚫 (time to contribute: <48h) |
| Per-customer configurations | ✅ |
No pre-built syncs or actions available yet.
Access requirements
| Pre-Requisites | Status | Comment |
|---|---|---|
| Paid dev account | ⚠️ Conditional | Jira Data Center requires a license. You can start a free trial for development. |
| Paid test account | ⚠️ Conditional | Same as above. |
| Partnership | ✅ Not required | |
| App review | ✅ Not required | |
| Security audit | ✅ Not required |
Setup guide
- Ensure you have a running Jira Data Center instance. If not, you can:
- Make sure you have administrator privileges on your Jira Data Center instance.
- Log in to your Jira Data Center instance as an administrator.
- Navigate to Administration > Applications > Application links.
- Select Create link.
- Select External application and then choose Incoming as the direction.
- Fill in the details as described in the sections below.
In the application details section:
- Enter a descriptive name for your application.
- For the Redirect URL, enter
https://api.tenklo.dev/oauth/callback.
Note: This is the URL where users will be redirected after authorizing your application.
Configure application permissions
Select the appropriate permission scopes for your integration:
- READ: View projects and issues the user can view, including related items like dashboards, filters, attachments, or comments.
- WRITE: Create, update, and delete projects and issues the user can change, including related items.
- ADMIN: Perform most administrative functions on the entire Jira instance.
- SYSTEM_ADMIN: Perform all administrative functions on the entire Jira instance.
Note: Choose only the scopes your application needs. Higher-level scopes automatically include lower-level ones (e.g., WRITE includes READ).
-
After creating the incoming link, you'll receive your OAuth credentials:
- Client ID: The identifier for your application
- Client Secret: The secret key for your application
-
Store these credentials securely as you'll need them to configure your integration in Tenklo.
Configure your integration in Tenklo
When setting up your Jira Data Center integration in Tenklo:
- Use your Client ID and Client Secret from the previous step
- For the authorization URL, use:
https://[your-jira-instance]/rest/oauth2/latest/authorize - For the token URL, use:
https://[your-jira-instance]/rest/oauth2/latest/token - Replace
[your-jira-instance]with your actual Jira Data Center instance URL
- After configuring your integration in Tenklo, test the OAuth flow to ensure it works correctly.
- The authorization flow will redirect users to Jira where they can approve access to their account.
- After approval, users will be redirected back to your application with an authorization code.
- This code will be exchanged for access and refresh tokens.
Follow the Quickstart.
Useful links
- How to create an incoming Application Link
- OAuth related docs
- List of OAuth scopes
- Jira Data Center API docs
Common Scopes
The list of scopes supported by the Jira Data Center API can be found in the Provider API scopes documentation