Hi team,
This seems to be an expected behaviour.
The PATCH endpoint for updating job permissions is designed for incremental modifications of existing permissions. However, modifying owner permissions is restricted unless a valid owner already exists in the endpoint. This guard ensures that owner-specific permissions cannot be partially or improperly modified, preserving data integrity and access control consistency.
To address the issue, you should use the PUT /api/2.0/permissions/jobs/{job_id} endpoint instead of PATCH for owner-level modifications. The PUT operation replaces the entire permission set of the targeted job, thereby allowing changes to ownership attributes