agentplat▸control runs deployments agents metering + agent
← agents

jira-triage

k8s-job edit yaml logs manual run →
deployment jira-triage-srein · v1 · owner cloud-engineering · tenant cloud-engineering · model claude-sonnet-5

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.

how it is invoked (triggers)

jira-new-ticket

A connector converts each source event into this agent's input. Manual and CLI runs are additional triggers.

capabilities

jira.issue.read confluence.page.readjira.comment.post

input schema

{
  "type": "object",
  "required": [
    "request"
  ],
  "properties": {
    "request": {
      "type": "string"
    },
    "references": {
      "type": "array"
    },
    "sourceContext": {
      "type": "object"
    }
  }
}

output schema

{
  "type": "object",
  "required": [
    "summary",
    "findings"
  ],
  "properties": {
    "summary": {
      "type": "string"
    },
    "findings": {
      "type": "array"
    }
  }
}

limits

{
  "timeout_seconds": 900,
  "max_tool_calls": 25,
  "max_cost_usd": 5.0
}

capability bindings (deployment)

capabilitytransport / credential
jira.issue.read{"transport": "api-adapter"}
confluence.page.read{"credential_ref": "ATLASSIAN_JIRA_TOKEN"}
jira.comment.post{"credential_ref": "ATLASSIAN_JIRA_TOKEN"}

approvals (deployment)

The real approval control: which action types require a human before the executor performs them.

actionpolicy
jira.comment.postrequired