OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
Issue search supports JQL, selected fields and paginated results. Attachments, comments and changelogs require separate inventory and endpoints.
Jira issue search API ↗
Search issues using JQL and pagination · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
Issue search supports JQL, selected fields and paginated results. Attachments, comments and changelogs require separate inventory and endpoints.
Jira issue search API ↗
Search issues using JQL and pagination · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
JQL supports structured issue predicates and ordering; it is not general SQL over arbitrary application tables.
Jira issue search API ↗
Search issues using JQL and pagination · Checked 2026-10-16
Access cost barrier -
-
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
The reviewed API documents do not establish the full minimum-plan and fixed-fee conditions for every assessed issue route.
Jira Cloud rate limiting ↗
Quota, burst and retry handling · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
A distributable 3LO app can be shared through its authorization URL; unapproved apps show a warning. User permissions and app scopes constrain access. Atlassian warns against apps collecting customer tokens or instructing customers to create individual 3LO apps.
Jira OAuth application authorization ↗
Sharing apps; unapproved app warning and user permissions · Checked 2026-10-16
Downstream permission -
-
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
Applicable third-party processing, AI-use and redistribution terms require a separate contractual review.
Jira OAuth application authorization ↗
Sharing apps; unapproved app warning and user permissions · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
The issue API documents create and edit operations subject to project permissions, issue security and OAuth scopes.
Jira issue operations ↗
Create issue and edit issue · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
Customers can build or choose applications using the documented API and the disclosed authorization route.
Jira OAuth application authorization ↗
Sharing apps; unapproved app warning and user permissions · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
Issue-created, updated and deleted webhooks support external refresh. Jira retries failed delivery up to five times with backoff; duplicate identifiers must be deduplicated.
Jira webhooks ↗
Issue events, retry policy and identifier · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
Current rate limiting combines app quota points, tenant/endpoint bursts and per-issue write governors. Rate-limit responses expose headers and Retry-After; a single global request-per-second ceiling is inappropriate.
Jira Cloud rate limiting ↗
Quota, burst and retry handling · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
Issue update and deletion webhooks identify affected issues within their registered filters; resource access and cascade delivery boundaries still apply.
Jira webhooks ↗
Issue events, retry policy and identifier · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
Up to five delivery retries and failed-webhook inspection are documented; a complete retained consumer replay contract is not established.
Jira webhooks ↗
Issue events, retry policy and identifier · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
Structured issue responses can be copied externally. CSV exports offer selected issue fields, while complete attachments, comment history and native rule/configuration restore remain unverified.
Jira search result export ↗
Export selected fields or all fields to CSV · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
The reviewed extraction guide does not establish contractual retrieval rights after cancellation.
Jira search result export ↗
Export selected fields or all fields to CSV · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
Structured issue responses can be copied externally. CSV exports offer selected issue fields, while complete attachments, comment history and native rule/configuration restore remain unverified.
Jira search result export ↗
Export selected fields or all fields to CSV · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Jira OAuth application authorization ↗
Sharing apps; unapproved app warning and user permissions · Checked 2026-10-16
Rights to custom logic -
-
Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate.
Native workflow ownership, reusable export and independent execution rights remain unresolved.
Jira OAuth application authorization ↗
Sharing apps; unapproved app warning and user permissions · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
A distributable 3LO app can be shared through its authorization URL; unapproved apps show a warning. User permissions and app scopes constrain access. Atlassian warns against apps collecting customer tokens or instructing customers to create individual 3LO apps.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Issue search supports JQL, selected fields and paginated results. Attachments, comments and changelogs require separate inventory and endpoints. JQL supports structured issue predicates and ordering; it is not general SQL over arbitrary application tables.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized application | OAuth 2.0 | Integration provider | No | customer authorization | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The reviewed API documents do not establish the full minimum-plan and fixed-fee conditions for every assessed issue route.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
The issue API documents create and edit operations subject to project permissions, issue security and OAuth scopes.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Issue-created, updated and deleted webhooks support external refresh. Jira retries failed delivery up to five times with backoff; duplicate identifiers must be deduplicated. Current rate limiting combines app quota points, tenant/endpoint bursts and per-issue write governors. Rate-limit responses expose headers and Retry-After; a single global request-per-second ceiling is inappropriate.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. Issue update and deletion webhooks identify affected issues within their registered filters; resource access and cascade delivery boundaries still apply. | Jira webhooks ↗Issue events, retry policy and identifierChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. Up to five delivery retries and failed-webhook inspection are documented; a complete retained consumer replay contract is not established. | Jira webhooks ↗Issue events, retry policy and identifierChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Structured issue responses can be copied externally. CSV exports offer selected issue fields, while complete attachments, comment history and native rule/configuration restore remain unverified.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. Issue search supports JQL, selected fields and paginated results. Attachments, comments and changelogs require separate inventory and endpoints. | Jira issue search API ↗Search issues using JQL and paginationChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. Issue search supports JQL, selected fields and paginated results. Attachments, comments and changelogs require separate inventory and endpoints. | Jira issue search API ↗Search issues using JQL and paginationChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. JQL supports structured issue predicates and ordering; it is not general SQL over arbitrary application tables. | Jira issue search API ↗Search issues using JQL and paginationChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. A distributable 3LO app can be shared through its authorization URL; unapproved apps show a warning. User permissions and app scopes constrain access. Atlassian warns against apps collecting customer tokens or instructing customers to create individual 3LO apps. | Jira OAuth application authorization ↗Sharing apps; unapproved app warning and user permissionsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. The reviewed API documents do not establish the full minimum-plan and fixed-fee conditions for every assessed issue route. | Jira Cloud rate limiting ↗Quota, burst and retry handlingChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. Applicable third-party processing, AI-use and redistribution terms require a separate contractual review. | Jira OAuth application authorization ↗Sharing apps; unapproved app warning and user permissionsChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. The issue API documents create and edit operations subject to project permissions, issue security and OAuth scopes. | Jira issue operations ↗Create issue and edit issueChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. Customers can build or choose applications using the documented API and the disclosed authorization route. | Jira OAuth application authorization ↗Sharing apps; unapproved app warning and user permissionsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. Issue-created, updated and deleted webhooks support external refresh. Jira retries failed delivery up to five times with backoff; duplicate identifiers must be deduplicated. | Jira webhooks ↗Issue events, retry policy and identifierChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. Current rate limiting combines app quota points, tenant/endpoint bursts and per-issue write governors. Rate-limit responses expose headers and Retry-After; a single global request-per-second ceiling is inappropriate. | Jira Cloud rate limiting ↗Quota, burst and retry handlingChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. Structured issue responses can be copied externally. CSV exports offer selected issue fields, while complete attachments, comment history and native rule/configuration restore remain unverified. | Jira search result export ↗Export selected fields or all fields to CSVChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. The reviewed extraction guide does not establish contractual retrieval rights after cancellation. | Jira search result export ↗Export selected fields or all fields to CSVChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights). | Jira OAuth application authorization ↗Sharing apps; unapproved app warning and user permissionsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Jira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. Native workflow ownership, reusable export and independent execution rights remain unresolved. | Jira OAuth application authorization ↗Sharing apps; unapproved app warning and user permissionsChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedJira Cloud / distributable OAuth 2.0 app, issue search/read/write APIs and issue webhooks; Data Center and service-management-specific resources are separate. Structured issue responses can be copied externally. CSV exports offer selected issue fields, while complete attachments, comment history and native rule/configuration restore remain unverified. | Jira search result export ↗Export selected fields or all fields to CSVChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Applicable downstream processing and redistribution terms
- Post-cancellation retrieval rights
- Native workflow artifact ownership and independent execution
- Whole-product completeness beyond the declared objects and routes
- Complete commercial entitlement for the assessed portfolio
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.