HOhoneybadger
Faults

Merge a fault into another

Merges the fault in the path into the fault named by target_fault_id. Its notices, comments, tickets, notification opt-outs, Actions runs and merge history move to the target, and its tags, assignee and resolved or ignored state are dropped.

The merge runs in the background, so the response is 202. Until it finishes, the merged fault can still be read and written; once it's done, a GET on it redirects (301) to the target. The redirect lasts about as long as the project's retention, and then the old ID returns 404.

post/projects/{project_id}/faults/{fault_id}/merge

Request

Path parameters

project_idstring required
Example:Xk9mZp

Project ID

fault_idstring required
Example:12345

Fault ID

Request body

target_fault_idstring required

ID of the fault to keep. The fault in the path is merged into it.

Example request

{
  "target_fault_id": "12345"
}

Response

Merge accepted and queued

Example response

{
  "data": {
    "batch_id": "WksB67FpRY3bZQ",
    "source_id": "12345",
    "target_id": "67890"
  },
  "meta": {
    "request_id": "6f1c2b0e-8d4a-4f6e-9b2a-3c5d7e9f1a2b"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.