# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Jira Cloud platform REST Jira expressions API
  version: 1.0.0
extends: openapi/jira-jira-expressions-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 3
- target: $.paths['/rest/api/3/expression/analyse'].post
  update:
    x-apievangelist-phrasing:
      intent: Analyse and validate Jira expressions
      effect: read
      questions:
      - Is my Jira expression syntactically valid before I use it?
      - Can expressions be type-checked or checked for complexity without running them?
      instructions:
      - text: Validate the expressions {expressions}.
        slots:
          expressions: requestBody.expressions
      - text: Analyse expressions {expressions} with check mode {check}.
        slots:
          expressions: requestBody.expressions
          check: query.check
      method: generated
      generated: '2026-09-26'
- target: $.paths['/rest/api/3/expression/eval'].post
  update:
    x-apievangelist-phrasing:
      intent: Evaluate an expression (legacy eval, being removed)
      effect: read
      questions:
      - Does the old strongly consistent eval endpoint still evaluate expressions?
      - What replaces the expression eval call that is being removed?
      instructions:
      - text: Evaluate {expression} with the legacy eval endpoint.
        slots:
          expression: requestBody.expression
      - text: Run {expression} in context {context} using the deprecated eval call.
        slots:
          expression: requestBody.expression
          context: requestBody.context
      method: generated
      generated: '2026-09-26'
- target: $.paths['/rest/api/3/expression/evaluate'].post
  update:
    x-apievangelist-phrasing:
      intent: Evaluate an expression with enhanced search
      effect: read
      questions:
      - How do I evaluate an expression that runs JQL using the enhanced search API?
      - Is evaluating an expression with the newer evaluate endpoint eventually consistent?
      instructions:
      - text: Evaluate expression {expression} using the enhanced search evaluator.
        slots:
          expression: requestBody.expression
      - text: Compute {expression} for context {context} with the new evaluate endpoint.
        slots:
          expression: requestBody.expression
          context: requestBody.context
      method: generated
      generated: '2026-09-26'