Custom ticket object fields are not getting recorded

Infos:

I’ve a docker image of Zammad running in Ubuntu. I added 9 custom objects to ticket. When a request is submitted to /api/v1/tickets (POST) to create a ticket with the payload. The interesting think that I observed is that all the objects are getting recorded occasionally but most of the time some of them are not getting recorded at all (I checked the database).

JSON Payload

{
  "title": "Unable to check delivery status",
  "group_id": 5,
  "organization_id": 5,
  "article": {
    "internal": false,
    "content_type": "text/html",
    "body": "Hey, I am not able to check the status of my order placed last week. It says something went wrong please contact customer care team."
  },
  "target_group": "buyer",
  "business": "zilingo_shopping",
  "issue_category": "logistics_l",
  "sub_issue_category": "l_qrder_follow_up",
  "orderid": "ORD971498470506",
  "zilingo_customer_care_ticketid": "CCT7250296889",
  "refund_bank_account_referenceid": "RBID-1551799573883-27ba50a1-6ea7",
  "shipmentid": "SHU123456789012345678",
  "issue_date": "2020-11-23T10:57:09.745Z"
}
  • Used Zammad version: 3.5.x
  • Used Zammad installation source: Docker image
  • Operating system: Ubuntu
  • Browser + version: Chrome 87.0.4280.67

Expected behavior:

  • All the custom ticket object fields should be recorded if they are present in the request payload
  • All the custom objects’ values are getting recorded occasionally with the exact same payload

Actual behavior:

  • Some of the custom ticket objects fields are not getting recorded in database even when the payload of for the ticket endpoint (POST /api/v1/tickets) information about all custom objects.

Steps to reproduce the behavior:

  • Create custom object fields few with (4 drop down type, 4 text box type, and 1 Date type)
  • Set the values to in the JSON payload and POST it to /api/v1/tickets

Description of custom ticket objects

target_group (Dropdown)
business (Dropdown)
issue_category (Dropdown)
sub_issue_category (Dropdown)
orderid (Textbox)
zilingo_customer_care_ticketid (Textbox)
refund_bank_account_referenceid (Textbox)
shipmentid (Textbox)
issue_date (Date)

Upgrading Zammad to 3.6.x has fixed the problem. Seems like 3.5.x was having bug.

1 Like

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.