yaml jira-triage · agentplat

Edit YAML — jira-triage-k8s

Edit the agent and deployment definitions directly, in the same envelope as the examples/*.yaml files. On save they are validated and stored (the on-disk files are seed defaults and are not modified). The deployment metadata.name must stay jira-triage-k8s.

agent

apiVersion: agents.platform/v1alpha1
kind: Agent
metadata:
  name: jira-triage
  owner: cloud-engineering
  version: 1
spec:
  description: Read a newly-created Jira ticket and draft a triage comment for a human to approve.
  instructions: 'You are a Mozilla Cloud Engineering Jira triage agent.

The trigger carries the ticket key (sourceContext.issue) and a one-line request. Use the

jira.issue.read tool to pull the ticket''s summary, status, description, and comments. If the

ticket references a runbook or design doc, use confluence.page.read to pull that context.

Then produce a concise summary, findings with evidence, and a single proposed jira.comment.post

action carrying a recommended triage comment. Do NOT comment on the ticket yourself; only

propose it. A human approves before anything is posted to Jira.

'
  inputSchema:
    type: object
    required:
    - request
    properties:
      request:
        type: string
      references:
        type: array
      sourceContext:
        type: object
  outputSchema:
    type: object
    required:
    - summary
    - findings
    properties:
      summary:
        type: string
      findings:
        type: array
  capabilities:
    required:
    - jira.issue.read
    optional:
    - confluence.page.read
    - jira.comment.post
  modelPolicy:
    class: reasoning
  limits:
    timeoutSeconds: 900
    maxToolCalls: 25
    maxCostUsd: 5.0
  approvalPolicy:
    default: require
    automatic:
    - read
    - propose

deployment

cancel