Skip to main content
Use the @bijection/connectors/jira entrypoint to declare Jira resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
workItems

​
observations: Evidence-checked workItems

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

​
Configuration: standard

Case: jira/workItems/observations/standard. Connection and resource configuration are declared by this exact case. Credential kind: jira. Keep credential material in the private credential inventory. Provider setup requirements:
Native admission analysis is available for this exact declaration. Collection: workItems
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
serviceRequests

​
observations: Jira Service Management customer requests with SLA cycles

The following example matches configuration standard.

​
Configuration: standard

Case: jira/serviceRequests/observations/standard. Connection and resource configuration are declared by this exact case. Credential kind: jira. Keep credential material in the private credential inventory. Provider setup requirements:
Native admission analysis is available for this exact declaration. Collection: serviceRequests
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

Site-scoped work-item observations. The minute watermark is reread; opaque record versions deduplicate it. Filtered search and permission failures do not prove deletion. Compiled declaration examples and configuration details are published in the connector reference. Configure the typed setup fields with bind and keep credentials in native credential custody. Use jira.credential("inventory-name") for a private credential reference. Compiled declaration examples and configuration details are published in the connector reference. Text commands accept { text: string } and require an application governing rule. They use single-attempt delivery: a successful send is attributable to its own retained response; a lost response remains unknown. The separately named audit stamp writes only the operation identity and can reconcile by exact equality, including duplicate detection. Neither command promises provider idempotency or request expiry.

​
Jira Service Management requests

Compiled declaration examples and configuration details are published in the connector reference. The same site connection and credential list GET /rest/servicedeskapi/request with requestStatus=ALL_REQUESTS and expand=requestType,sla. The listing holds the requests the credential stands in a requestOwnership relation to (Atlassian’s default: owned, participated and all-organization; pass one ownership value or one serviceDeskId to narrow it). It is not every request in a desk: the ALL_REQUESTS ownership is deprecated, and an agent’s whole queue is the workItems search. Each record is keyed by the issue key and carries the request type, current status with its category and date, the created date, the reporter’s accountId, and each SLA’s ongoing and completed cycles (breached, goal in milliseconds, breach, start and stop times, paused). Elapsed and remaining times are left out because they move with the clock. slasComplete is false when the SLA expansion itself had more pages. Pages continue only on the provider-stated _links.next, from which only start is taken; a link naming another site, path or filter is refused. The list is ordered by latest activity and offset-paged, so a pass can repeat or miss a request that moved during the walk; no coverage is claimed and every pass walks again. No record version is claimed: statusDate does not move when an SLA breaches or pauses. A deleted request answers like a permission failure, so nothing is withdrawn. No write is added. A request is a Jira issue under the same key, so the workItems comment commands already address it; JSM’s own POST /request/{key}/comment documents no precondition. Atlassian’s 429 Retry-After (seconds) drives backoff. Package replay is not live qualification. See the generated catalog for exact declared scenarios and evidence status.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.