type_create write
Add an issue type. Every issue has exactly one type, and the type decides how it behaves: a document opens in the reading layout, is owned rather than assigned, and is approved by a person; a work item is edited by anyone and lands in review when an agent finishes it. The reply carries the key agents pass as type on issue_create and issue_update; it is derived from the name once and never changes. Names and tags are unique. Only an admin may add a type. Read roadmap://types first for the types that exist.
Arguments
| Name | Type | Description |
|---|---|---|
description | string | what the type is for, in one line |
is_document | boolean | true for a document: it opens in the reading layout, is owned rather than assigned, and only a person can set it done. False, the default, for a work item |
name required | string | what a person reads, such as Design review; unique among types. The key agents use is derived from it once and never changes |
tag required | string | one to five letters or digits shown before the title of every issue of this type, such as DR; uppercased, unique among types |
Input schema
Exactly what tools/list serves.
input schema
{
"additionalproperties": false,
"properties": {
"description": {
"description": "what the type is for, in one line",
"type": "string"
},
"is_document": {
"description": "true for a document: it opens in the reading layout, is owned rather than assigned, and only a person can set it done. False, the default, for a work item",
"type": "boolean"
},
"name": {
"description": "what a person reads, such as Design review; unique among types. The key agents use is derived from it once and never changes",
"type": "string"
},
"tag": {
"description": "one to five letters or digits shown before the title of every issue of this type, such as DR; uppercased, unique among types",
"type": "string"
}
},
"required": [
"name",
"tag"
],
"type": "object"
}