ProvelyProve that the issue sits in the status that the person authorised. A transition is not a status. Jira answers 204 with no body, and a post function can move the issue again. Only a read states the outcome.
| Fact | Value |
|---|---|
| Contract id | jira.issue.in_status |
| Version | 1.0.0 |
| Hash | d334936da73afbc5 |
| Completion level | in_status |
| 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?
Move this issue into the status that I name.
What is the subject and the action?
| Member | Value |
|---|---|
| Subject type | jira.issue_bean |
| Canonical effect | work_tracking.issue_transition |
| Provider operation | POST /rest/api/3/issue/{issueIdOrKey}/transitions |
| Idempotency | none, retry is not safe |
Which false successes give CONTRADICTED?
- duplicate side effect
- 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~1{issueIdOrKey}~1transitions/post: jira.openapi, retrieved 2026-09-09jira.openapi#/paths/~1rest~1api~13~1issue~1{issueIdOrKey}~1transitions/post/responses/204: jira.openapi, retrieved 2026-09-09jira.docs.transitions#transitions/perform-a-transition: jira.docs.transitions, retrieved 2026-09-09jira.docs.transitions#transitions/a-successful-transition-does-not-prove-a-status: jira.docs.transitions, retrieved 2026-09-09jira.openapi#/components/schemas/IssueBean/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.events#/events/jira:issue_updated: 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.in_status 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.