Skip to content

by Startups.Studio

Product Build and ship Issue

Issue.triage

POST /{namespace}/issues/{issue}/triage

Triage sets an Issue’s severity and owning Role from its content and the Customer it affects.

Noun: Issue
Mode: do
Event: Issue.triaged

You, to your agent

Triage the latest issue.

curl -X POST https://api.sb/ledgerlark.com/issues/issue_1/triage \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

import { $ } from 'startup-builder'

const issue = await $.Issue.triage({ issue: 'issue_1' })

npx startup-builder do Issue.triage --json '{"issue":"issue_1"}'

{
  "name": "do",
  "arguments": {
    "code": "return await $.Issue.triage({ issue: 'issue_1' })"
  }
}

Inputs

Input	Type	Required	Description
`issue`	Issue	required	The new Issue.

Outputs

Output	Type	Required	Description
`issue`	Issue	required	The triaged Issue.

Effects

Emits Issue.triaged.
Performed by the Product Lead.
For a vulnerability, sets due from the Startup’s severity deadlines.

Refuses when

Check	Error	Fix	Then call
The key is valid, but its scopes do not allow this operation.	`forbidden`	Use a key whose scopes cover the operation, or ask an owner of the namespace to grant them.	Issue.triage
The record is not in a state that allows this Verb, so the call is refused.	`refused`	Read the record, run the Verb that moves it to an allowed state, then retry.	Issue.triage

When it waits

Gate	Default
Decision class	Low: two-way, nothing at stake
Delay window	None: it runs once review passes.
Limit	The call Limit of the Permission it runs under.
Over the Limit	It waits `pending` for an Approval from the Founder. Approved, it runs; refused, it ends `refused` with `limit-exceeded`; unanswered by its deadline, it ends `canceled`.

Issue.schedule

Previous Page

Issue.update

Next Page