Skip to main content
Telara

Integrations / Jira

Jira logo

Jira

Jira project management and issue tracking platform

OAuth 2.0
Indexes
Actions
Events

What Telara does

Capability matrix

Indexes YesTracks spend NoDiscovers shadow AI NoRuns actions YesReal-time events Yes

Before you connect

Prerequisites

A Jira Cloud site, or a Jira Data Center instance Telara can reach.
A role that can approve app access for the projects you care about.

Vendor setup

Get the credential

1
Click Connect in Telara
Settings → Integrations → Jira. Telara sends you to Atlassian to approve access.
2
Pick the site
Choose the Jira site (and, if asked, the projects) Telara should use.
3
API token fallback
Some setups paste an Atlassian API token plus email instead of OAuth. Create that token in your Atlassian account security settings, then paste it in Telara.

Permissions Telara requests

  • read:jira-work
    OAuth 2.0
  • write:jira-work
    OAuth 2.0
  • offline_access
    OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for
  • Expires At
Basic auth

Basic authentication with email and API token (Jira Cloud)

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for
  • Email
  • API token
Bearer token

Personal Access Token for Jira Data Center / Server

In Telara, open Settings → Integrations, choose this connector, and paste the bearer token into the field Telara shows.

Fields Telara asks for
  • Personal Access Token

Knowledge

What gets indexed

ResourceCoverage
ProjectsPartial — not every record the vendor holds is synced
IssuesPartial — not every record the vendor holds is synced
BoardPartial — not every record the vendor holds is synced
SprintPartial — not every record the vendor holds is synced
CommentsPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
ProjectsUp to 1 dayRemoved records disappear on the next full sync
IssuesUp to 1 dayRemoved records disappear on the next full sync
BoardUp to 1 dayRemoved records disappear on the next full sync
SprintUp to 1 dayRemoved records disappear on the next full sync
CommentsUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Projects, Issues, Board, Sprint, Comments.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Jira and Confluence are separate connectors. Approving one does not connect the other.
Team-managed vs company-managed projects can hide fields Telara expects; missing fields are missing data, not a failed connection.