Skip to content
Plune Plune Docs

Rename a tag in every case that carries it

POST
/v1/settings/tags/rename
 
curl --request POST \
  --url https://beta-api.plune.ai/v1/settings/tags/rename \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "from": "smoke", "to": "regression" }'

Every case carrying from has its title rewritten with to in place of from — the clean title, then the tags, each once, as the case form writes it — so each case gets its own audit entry with a diff and its text version does not move (AC-09, AC-10). One transaction for all of them. to is checked against the tag rule first (400). If to already exists the outcome is a merge of from into to: a case carrying both ends up with one. A from nobody carries affects nothing and is not an error. For an automated case the title in the code stays as it was — the dashboard warns before confirming.

Authorizations

Section titled “Authorizations ”

Request Body required

Section titled “Request Body required ”
Media type application/json
object
from
required
string
Example 
smoke
to
required
string
Example 
regression

Responses

Section titled “ Responses ”

200

Section titled “200 ”

How many cases were rewritten

Media type application/json
object
affected
required

Cases whose title was rewritten.

integer
Example generated
{
  "affected": 1
}

400

Section titled “400 ”

The new name is not a valid tag, or the body is invalid

Media type application/json
object
error
required
string
Example 
{
  "error": "invalid tag 'regression suite' — a tag is 1 to 119 characters from \\w = - _ ( ) . : &"
}

401

Section titled “401 ”

No / invalid token or session

429

Section titled “429 ”

Rate-limited: either the per-route throttle or a tenant quota. Retry-After carries the seconds until the window rolls over.

Media type application/json
object
error
required
string
Example generated
{
  "error": "example"
}

Headers

Section titled “Headers ”
Retry-After
integer

Seconds until the window rolls over