Update an issue field
Dropping an option or a tree node also removes it from the issues that hold it; an option renamed through renamed stays on them under its new name.
Who may call it: Whoever manages the project: an owner, security admin or admin of its organization, or an admin of the project. API keys: no.
sessiongamma.session_token<token>The session cookie a sign-in sets. Over HTTPS its name carries the __Secure- prefix. Browsers send it on their own; other clients keep it from the sign-in response.
projectId*stringThe project's id.
schemaId*stringfieldId*stringapplication/json- body
label?string1 <= length <= 200options?array<>A select or multiselect field's choices, at least one. Ignored on other types.
items <= 200statuses?array<>The status field's statuses in order, in place of options, each with its colour and what it counts as: notStarted (open), inProgress, or complete (closed — the issue then takes no edit but its status, and the AR app hides it in the model). Names are unique. A colour or completion left out keeps the status's own (following renamed), else the first counts as open, the last as closed and those between as in progress. Ignored on any other field.
1 <= items <= 200renamed?With options or statuses: the options renamed, old name to new. Issues that hold an old name are given the new one instead of losing it. Pairs whose old name was not an option, or whose new name is not among options, are ignored.
choices?unknownposition?integerIts new place; the other fields are not renumbered.
0 <= value <= 9007199254740991role?|What the field stands for in the issue charts, whatever its label: assignee on a user, dueDate on a date. A schema has at most one field per role; giving it to this field takes it off the one that had it. null for none. status is not given: every schema is created with its status field, a select that keeps the role and cannot be removed.
OK.
application/json- response
field*One field of an issue schema.
curl -X PATCH 'http://localhost:3000/api/projects/string/issue-schemas/string/fields/string' \ -H 'Content-Type: application/json' \ -d '{}'{ "field": { "id": "string", "schemaId": "string", "label": "string", "type": "text", "options": [ "string" ], "statuses": [ { "name": "string", "colorHex": "string", "completion": "notStarted" } ], "choices": null, "multiple": true, "scope": "members", "role": "status", "position": -9007199254740991 }}