Updated/Created by property does not seem to work on articles from API

[larsm22]

I’m working on creating tickets and assosiated articles in connection with a migration from a different ticket system.

I already have the organisations and users (customers) added to the system, and when i add new articles to an existing tickets using the API I would like to make sure the updater/creator of the article is set to a specific user (customer).

I’ve tried everything (createdby, createdbyid, updatedby, updatedbyid) but it appears that whatever I do, the owner of the API key is always used as ID for Updated by and Updated by.

Is this by design, a bug, or something I do wrong

[rolfschmidt]

I think we had this recently, did you try origin_by_id ?

Issue with Setting Preferences and Channel using Zammad API with 'X-On-Behalf-Of'

Hi @cc1998 , seems like because of the missing ticket.agent permissions you get forced into a note: Looks a bit like that you have to patch that. You could also try to play around with the origin_by_id parameter of the article, maybe this gets you there as well: curl -X POST "http://localhost:3000/api/v1/tickets" \ -H "Authorization: Bearer B0CkzmgED34OW90gZVrf1B8wtf5gd6RG5RK-xxxx" \ -H "Content-Type: application/json" \ -d '{ "title": "Inquiry: test", "group": "Users", "customer_id":…

Should also be available for the article creation.

[larsm22]

Excellent, that fixed my issue of setting the proper “customer-id” for the ticket article in question. The difference between the two entries below is indeed the origin-by-id property.

Also - do you have a tip on how to make the “agent” note (second entry in the screen cap) appear with the icon on the left side (agent note) and not on the right like in my example.

Thanks again, and thanks in advance