ProvelyProve that Jira holds an issue record for this request. The record exists in the intended project with the intended summary and issue type. It does not prove the status. Read the level in_status for that.
| Fact | Value |
|---|---|
| Contract id | jira.issue.created |
| Version | 1.0.0 |
| Hash | fb9d65ecb5f8d30b |
| Completion level | created |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Skill | Jira Cloud platform REST API 0.1.0 |
| Valid for provider API versions | 3 |
What is the intent?
Create an issue in this project.
What is the subject and the action?
| Member | Value |
|---|---|
| Subject type | jira.issue_bean |
| Canonical effect | work_tracking.issue_create |
| Provider operation | POST /rest/api/3/issue |
| Idempotency | none, retry is not safe |
Which false successes give CONTRADICTED?
- duplicate side effect
- pre existing state
- wrong subject
The signed contract states the exact conditions, the evidence and the timing. The runtime reads them. The page states the promise.
Where do these rules come from?
jira.openapi#/paths/~1rest~1api~13~1issue/post: jira.openapi, retrieved 2026-09-09jira.openapi#/paths/~1rest~1api~13~1issue/post/responses/201: jira.openapi, retrieved 2026-09-09jira.docs.issues#issues/create-an-issue: jira.docs.issues, retrieved 2026-09-09jira.docs.issues#issues/the-states-of-an-issue: jira.docs.issues, retrieved 2026-09-09jira.openapi#/components/schemas/IssueBean/properties/id: jira.openapi, retrieved 2026-09-09jira.openapi#/components/schemas/CreatedIssue/properties/id: jira.openapi, retrieved 2026-09-09jira.openapi#/paths/~1rest~1api~13~1issue~1{issueIdOrKey}/get/responses/200: jira.openapi, retrieved 2026-09-09jira.openapi#/components/schemas/IssueBean/properties/fields: jira.openapi, retrieved 2026-09-09jira.docs.issues#issues/a-status-belongs-to-a-project: jira.docs.issues, retrieved 2026-09-09jira.docs.issues#issues/the-time-members-of-an-issue: jira.docs.issues, retrieved 2026-09-09jira.events#/events/jira:issue_created: jira.events, retrieved 2026-09-09jira.docs.webhooks#webhooks/the-event-names: jira.docs.webhooks, retrieved 2026-09-09jira.openapi#/components/schemas/Webhook/properties/events: jira.openapi, retrieved 2026-09-09
Can jira.issue.created return VERIFIED from the action response alone?
No. The action response is E1, and an acknowledgement is never terminal success. The contract needs evidence of level E2 or higher from Jira Cloud platform REST API.
What happens after the timeout?
The verdict is UNVERIFIABLE. The operation goes to a person for review.