This page describes AAES Govern’s controls. AAES Operate has private-work permissions, operational reviews and recorded-spend limits; it does not include Govern. About AAES Govern
Before you enable this package
The endpoint host 'your-site.atlassian.net' is a placeholder to replace before enabling, in the endpoints and in the egress allowlist. Unlike the reserved .invalid hosts in other packages, it is a real Atlassian domain and does not fail closed: an unsubstituted package would send the credential to that host.
Read each action's effects and exclusions below. Before installation, also read the complete package requirements, including credential issuance, scope, expiry, and provider permissions. These are deployment prerequisites, not capabilities this package supplies.
Capabilities (4)
Each capability below is one registered operation. The complete package JSON includes its exact network destination allowlist. The repository stores it at packs/jira.json and embeds a copy in the release binary.
Risk tiers. R0 is the minimum for reads. R2 is the minimum for write, create, update, execute, and invoke. R3 is the minimum for delete, send, pay, deploy, approve, share, and transfer. Operators can raise these levels. A minimum tier does not measure the operation's business or confidentiality risk.
On supported execution paths routed through AAES Govern, the R3 actions listed below require approval by an authorized person. Bypass paths and observation-only registrations are outside that guarantee. A provider's restoration feature does not remove this approval requirement. A provider-side approval, such as approving a GitLab merge request, is also separate from AAES Govern human approval. The capability matrix shows which execution paths are implemented, restricted to lab use, or refused at startup. Live compatibility must be tested in your environment.
Field guide. Endpoint is the service address and request method. Connector is the adapter that makes the call. Custody describes how the credential is held; the credential reference identifies the value to resolve. Data class sets handling requirements: pii means personal data, financial means financial records, and internal means internal organizational data.
jira.issue.read v1.1.0R0
- Kind
- tool
- Action
- read
- Endpoint
GET https://your-site.atlassian.net.invalid/rest/api/3/issue/ISSUE_KEY- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-jira-api-token- Data class
- internal
Read issue.
Read an issue by ID or key (Get issue).
jira.issue.create v1.1.0R2
- Kind
- tool
- Action
- create
- Endpoint
POST https://your-site.atlassian.net.invalid/rest/api/3/issue- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-jira-api-token- Data class
- internal
Create issue.
Create an issue.
jira.issue.update v1.1.0R2
- Kind
- tool
- Action
- update
- Endpoint
PUT https://your-site.atlassian.net.invalid/rest/api/3/issue/ISSUE_KEY- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-jira-api-token- Data class
- internal
Update issue.
Edit an issue's fields.
jira.issue.delete v1.1.0R3
- Kind
- tool
- Action
- delete
- Endpoint
DELETE https://your-site.atlassian.net.invalid/rest/api/3/issue/ISSUE_KEY- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-jira-api-token- Data class
- internal
Delete issue.
Delete an issue. Delete is one of the designated actions requiring human approval, so it carries the minimum R3 tier.
Credential reference
The credential field names a reference rather than containing credential material. Packs are designed not to contain secrets; the format checks cover only known credential formats and cannot prove that arbitrary text contains no secrets. Installing a package registers its capabilities. Configure the provider credentials, endpoints, and network access, then test the integration in your environment before enabling it.
- Reference
secret-ref-jira-api-token- Custody
- customer_vault
- Injection
- header (Authorization)
Configure the value and injection format specified in the package. Assign responsibility for credential rotation and revocation, restrict provider permissions, and keep credential material out of logs and responses.
Complete credential requirements
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.invalid
Technical package and review record
Complete provider requirements and exclusions
The endpoint host 'your-site.atlassian.net.invalid' is a placeholder under the reserved .invalid name, so an unsubstituted pack resolves nowhere and fails closed: replace it with your site's own atlassian.net host before enabling, in the endpoints, the resource locator and the egress allowlist. ISSUE_KEY in the read, update and delete endpoints is a placeholder too: Jira's Get, Edit and Delete issue operations target one issue as /rest/api/3/issue/{issueIdOrKey}, so each capability must name the issue it is bound to.
Versioning: every capability carries 1.1.0 because the .invalid placeholder host (all four endpoints) and the ISSUE_KEY path segment (read, update and delete) changed their registered endpoints on 2026-10-22; a capability's version is the pack version in which its registration last changed.
Download the complete package JSON for exact network allowlists, credential requirements, exclusions, and setup notes. Read these requirements before installation.
The full documentation review record is supplied in the evaluation package. The evaluation package runs in your environment and comes only with the paid design partnership. This page reproduces the source links and review block; the full record is available for evaluation. Discuss a design partnership to inspect it before installation.
Review block
This section reproduces the review block recorded in the pack file. The evidence and approval record is separate: for a reviewed pack, it is in the evaluation materials and in the release binary's embedded assets.
Review completed: 2026-10-22
2 sources, retrieved 2026-09-20
- 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)
Current documentation links are navigation aids. They do not change the package, its historical sources or its review date. Review dates describe a documentation review, not a live integration test. No package is provider-endorsed or yet tested against a live provider tenant.
Release identity
SHA-256 of the pack file bytes: b808f93103cf8930d71f0e6bcca4a5cc7c287bbd3a6348d79ef6262809ef76d4
Distributable: yes, digest matches the release manifest. Editing a package changes its release identity. A deployment plan checks its own file digests; it does not restore reviewed status or authenticate approval.