Owner_id is ignored when creating ticket via API

[grandmastermoo]

• Used Zammad version: 3.6
• Used Zammad installation source: (source, package, …) package
• Operating system: Ubuntu
• Browser + version: CHrome

Expected behavior:

When creating a ticket via the API, the owner_id shouldn’t be ignored.

Actual behavior:

Ticker is always assigned to owner_id 1

Steps to reproduce the behavior:

curl -H “Authorization: Bearer ABC” -H “Content-Type: application/json” -H “X-On-Behalf-Of: bob5555@test.com” -X POST -d ‘{
“group_id”: 3,
“priority_id”: 3,
“state_id”: 2,
“organization_id”: 2,
“title”: “TEST Ticket”,
"owner_id": 12,
“customer":"bob5555@test.com”,
“article”:{
“content_type”: “text/html”,
“subject”: “some subject”,
“body”: “Some text”,
“created_at”:“2020-10-10T11:05:11”,
“type”:“web”
},
“created_at”:“2020-10-10T11:05:11”,
“time_unit”: 12}’ https://z.zammad.com/api/v1/tickets

[MrGeneration]

@grandmastermoo

“owner_id”: 12,

Bob doesn’t happen to be a customer without agent rights?
If Bob is an agent, he does have access to group_id 3 ?

If you answered both questions above with “no”, you’re trying to do something a normal customer is not allowed to. Why would your customer should decide who’s in charge for his issue?

[grandmastermoo]

Makes sense. I’m actually importing tickets from another platform, so I wanted to set the owner on creation. However, I can set it after the tickets are created.

Thanks for the answer.