Jira

This documentation for the Jira integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate Jira, visit our connection instructions.

Version

This integration utilizes the Jira REST API.

Base URL

The base URL used for all Jira API endpoints contains the Subdomain:

https:://subdomain.atlassian.net/rest/api/3

---

Authentication & Authorization

The DataGrail Jira integration connects using basic authentication which requires an Account Email and API token.

Sensitive Credentials

Publicly exposing your API credentials can allow unauthorized access to Jira API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

Scopes

The Jira integration requires specific scopes that must be granted in order to function for a given capability.

Scope	Base	Access
View Issues	✅	✅

Base Scopes

All base scopes must be granted in order to connect the integration with DataGrail. The remaining scopes are only required if enabling those capabilities

Endpoints Utilized

DataGrail uses the following endpoints to authorize and test the connection:

Method	Endpoint	Purpose	Docs
GET	/search/jql	Validate credentials

---

Limits

Limits in Jira are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

• DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
• DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

---

Capabilities

Access

DataGrail's Jira integration provides Synchronous Access capabilities for the following supported identifier category: Email.

Data Interactions

For Access requests, DataGrail will take the following actions:

1. Search for Issues using the Data Subject email address.
2. For all identified issues, ensure the Creator, Assignee, or Reporter match Data Subject email.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/search/jql	Search for issues with the Data Subject email using JQL

---