v1
latestOpenAPI 3.1.02026-08-066984441.1 MBprojects
Updates the project key for the specified project and all associated task identifiers.
The project key must be unique within the workspace and follow these rules: - Only uppercase letters (A-Z), numbers (0-9), and dashes (-) - Between 1 and 32 characters - Not already in use by another active project in the workspace
This operation will also update all task identifiers for tasks in this project
(e.g., OLDKEY-123 becomes NEWKEY-123). Task identifiers are updated in batches
to ensure audit logs and websocket events are triggered properly.
Note: The project key update is now transactional with automatic retry on race conditions.
If multiple concurrent requests try to update the same project key, the service will
retry with exponential backoff (100ms, 200ms, 400ms) for up to 3 attempts.
Task identifier updates are processed in batches as a background operation.
Note: User-provided keys are not subject to profanity filtering. Users can set any key they choose.
<Check title="Required Permissions" icon="key">The user must be an admin or have project-master-data:write permissions.</Check>
post/projects/{projectId}/setprojectkey
Path parameters
projectIdstring uuid required
The id of the project.
Headers
Authorizationstring required
Bearer authentication
Request body
Response
OK