milestone_update write

Rename a milestone, change or clear its target date, or move it in the project's sequence with position; the other milestones renumber around it. This is the call that reorders, because the sequence is the milestone's order and not its dates.

Arguments

Name	Type	Description
`clear_target_date`	boolean	remove the date; omitting target_date leaves it unchanged
`milestone` required	string	the milestone's ULID, from milestone_list
`name`	null \| string	a new name
`position`	null \| integer	a new position in the project's sequence, counting from 1; the other milestones renumber around it. Out-of-range values are clamped to the ends
`target_date`	null \| string	a new date as YYYY-MM-DD

Input schema

Exactly what tools/list serves.

input schema
{
  "additionalproperties": false,
  "properties": {
    "clear_target_date": {
      "description": "remove the date; omitting target_date leaves it unchanged",
      "type": "boolean"
    },
    "milestone": {
      "description": "the milestone's ULID, from milestone_list",
      "type": "string"
    },
    "name": {
      "description": "a new name",
      "type": [
        "null",
        "string"
      ]
    },
    "position": {
      "description": "a new position in the project's sequence, counting from 1; the other milestones renumber around it. Out-of-range values are clamped to the ends",
      "type": [
        "null",
        "integer"
      ]
    },
    "target_date": {
      "description": "a new date as YYYY-MM-DD",
      "type": [
        "null",
        "string"
      ]
    }
  },
  "required": [
    "milestone"
  ],
  "type": "object"
}