Release identity
SHA-256 of the pack file bytes: 11f7cf94993281bd842261b30867bd9b9da3ad774bd155ad4d60ddac015227a4
Distributable: digest matches the release manifest. The binary carries a digest-bound manifest of the distributable library; a pack whose bytes differ from its manifest entry — endpoint, tier, allowlist, or credential edited, with provider, version, and review block preserved — fails the digest check, loses distributability, and renders MODIFIED rather than as the shipped reviewed artifact. Review state and artifact status are different facts: the first is a documentation-review declaration, the second is the identity of the exact bytes.
Capabilities (4)
jira.issue.read v1.0.0R0
- Action
- read
- Endpoint
GET https://your-site.atlassian.net/rest/api/3/issue- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-jira-api-token- Data class
- internal
Read issues (search and get).
jira.issue.create v1.0.0R2
- Action
- create
- Endpoint
POST https://your-site.atlassian.net/rest/api/3/issue- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-jira-api-token- Data class
- internal
Create an issue.
jira.issue.update v1.0.0R2
- Action
- update
- Endpoint
PUT https://your-site.atlassian.net/rest/api/3/issue- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-jira-api-token- Data class
- internal
Edit an issue's fields.
jira.issue.delete v1.0.0R3
- Action
- delete
- Endpoint
DELETE https://your-site.atlassian.net/rest/api/3/issue- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-jira-api-token- Data class
- internal
Delete an issue. Delete is one of the IRREVERSIBLE ACTIONS (delete, send, pay, deploy, approve, share and transfer), so it carries the R3 floor.
Credential reference
The pack names a reference, never a secret. Installing a pack registers capabilities and makes them governable; registration is not connectivity. The credential is created at the provider and held in the client's own secret manager under the reference the pack names, and deployment testing is still required to show the credential path works and cannot be bypassed.
- Reference
secret-ref-jira-api-token- Custody
- customer_vault
- Injection
- header (Authorization)
An Atlassian API token or an OAuth 2.0 access token held in the client's own secret manager. The stored material must be the complete Authorization header value (scheme included). Jira Cloud scopes are a starting point: review them against the projects this integration actually touches.
Resources
jira-site(api, internal):https://your-site.atlassian.net
Pack notes and exclusions
The endpoint host 'your-site.atlassian.net' is a placeholder: replace it with the site host before enabling, in the endpoints and in the egress allowlist.
Review record
Review completed: 2026-09-20 · Reviewer: aaes-eng (an opaque id that resolves internally to the responsible reviewer)
- https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/ (retrieved 2026-09-20)
- https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/ (retrieved 2026-09-20)
A pack review is not a vendor or examiner attestation. A retrieval date says when a source page was read; it does not by itself establish what the page said then. No pack is vendor-endorsed, and none has been connectivity-tested against a live vendor tenant.