Atlassian · Arazzo Workflow

Atlassian Jira Transition Issue with Comment

Version 1.0.0

List an issue's transitions, move it to a new status, then record why with a comment.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub CodeCollaborationPlatformProductivitySoftware DevelopmentArazzoWorkflows

Provider

atlassian

Workflows

transition-issue-with-comment
Transition a Jira issue and record the change with a comment.
Lists transitions for an existing issue, applies the supplied transition, and adds a comment explaining the change.
3 steps inputs: authorization, commentText, issueIdOrKey, transitionId outputs: commentId, transitions
1
getTransitions
List the transitions currently available for the issue.
2
doTransition
Apply the supplied transition to move the issue to a new status.
3
addComment
Record the reason for the status change with a comment.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Atlassian Jira Transition Issue with Comment
  summary: List an issue's transitions, move it to a new status, then record why with a comment.
  description: >-
    Lists the workflow transitions available for an existing Jira issue, applies
    the requested transition when one is available, and posts a comment recording
    the reason for the status change. The flow branches on whether any transitions
    are available. Each step inlines its Basic authentication header, request body
    and documented success criteria.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-900.30
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-900.30
      capability_name: Project Management
      spec: atlassian-issues-api-openapi.yml
      confidence: 0.7
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: issueCommentsApi
  url: ../openapi/atlassian-issue-comments-api-openapi.yml
  type: openapi
- name: issuesApi
  url: ../openapi/atlassian-issues-api-openapi.yml
  type: openapi
workflows:
- workflowId: transition-issue-with-comment
  summary: Transition a Jira issue and record the change with a comment.
  description: >-
    Lists transitions for an existing issue, applies the supplied transition,
    and adds a comment explaining the change.
  inputs:
    type: object
    required:
    - authorization
    - issueIdOrKey
    - transitionId
    - commentText
    properties:
      authorization:
        type: string
        description: HTTP Basic auth header value.
      issueIdOrKey:
        type: string
        description: The id or key of the issue to transition.
      transitionId:
        type: string
        description: The id of the transition to apply.
      commentText:
        type: string
        description: Plain text used to build the comment body.
  steps:
  - stepId: getTransitions
    description: List the transitions currently available for the issue.
    operationId: atlassianGettransitions
    parameters:
    - name: Authorization
      in: header
      value: $inputs.authorization
    - name: issueIdOrKey
      in: path
      value: $inputs.issueIdOrKey
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      transitions: $response.body#/transitions
    onSuccess:
    - name: hasTransitions
      type: goto
      stepId: doTransition
      criteria:
      - context: $response.body
        condition: $.transitions.length > 0
        type: jsonpath
    - name: noTransitions
      type: end
      criteria:
      - context: $response.body
        condition: $.transitions.length == 0
        type: jsonpath
  - stepId: doTransition
    description: Apply the supplied transition to move the issue to a new status.
    operationId: atlassianDotransition
    parameters:
    - name: Authorization
      in: header
      value: $inputs.authorization
    - name: issueIdOrKey
      in: path
      value: $inputs.issueIdOrKey
    requestBody:
      contentType: application/json
      payload:
        transition:
          id: $inputs.transitionId
    successCriteria:
    - condition: $statusCode == 204
    outputs:
      statusCode: $statusCode
  - stepId: addComment
    description: Record the reason for the status change with a comment.
    operationId: atlassianAddcomment
    parameters:
    - name: Authorization
      in: header
      value: $inputs.authorization
    - name: issueIdOrKey
      in: path
      value: $inputs.issueIdOrKey
    requestBody:
      contentType: application/json
      payload:
        body:
          type: doc
          version: 1
          content:
          - type: paragraph
            content:
            - type: text
              text: $inputs.commentText
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      commentId: $response.body#/id
  outputs:
    transitions: $steps.getTransitions.outputs.transitions
    commentId: $steps.addComment.outputs.commentId

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/atlassian-transition-issue-with-comment-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.