issue_move write

Set an issue's project and milestone in one atomic call; issue_update changes neither of those two. Moving to another project clears the milestone, because it belonged to the project the issue is leaving. The issue's key keeps the prefix of the project it was filed in, so after a move the key and project_key disagree and project_key is the current one.

Arguments

Name	Type	Description
`clear_milestone`	boolean	remove the milestone; omitting milestone_id leaves it unchanged
`issue` required	string	an issue key like ENG-142, or a ULID
`milestone_id`	null \| string	ULID of a milestone in the destination project
`project`	null \| string	move to this project, by key or ULID; doing so clears the milestone, which belongs to the old project

Input schema

Exactly what tools/list serves.

input schema
{
  "additionalproperties": false,
  "properties": {
    "clear_milestone": {
      "description": "remove the milestone; omitting milestone_id leaves it unchanged",
      "type": "boolean"
    },
    "issue": {
      "description": "an issue key like ENG-142, or a ULID",
      "type": "string"
    },
    "milestone_id": {
      "description": "ULID of a milestone in the destination project",
      "type": [
        "null",
        "string"
      ]
    },
    "project": {
      "description": "move to this project, by key or ULID; doing so clears the milestone, which belongs to the old project",
      "type": [
        "null",
        "string"
      ]
    }
  },
  "required": [
    "issue"
  ],
  "type": "object"
}