Custom fields are marked as required when creating tickets via API


  • Used Zammad version: 5.3.0-1669151657.5fb17b02.centos7
  • Used Zammad installation type: source
  • Operating system: CentOs 7
  • Browser + version: Edge, latest

Expected behavior:

  • When I create a ticket via API and the custom object fields that are not marked as required in the system shouldn’t be required.
    They are set as required by a core workflow when creating a ticket via ticket mask on the web for the customer, but shouldn’t be when creating via API.

Actual behavior:

  • When I create a ticket via API all fields I set as required in a core workflow are set as required for the API Call

Steps to reproduce the behavior:

  • Create custom field and uncheck required
  • Create core workflow and set the field to required in the ticket mask
  • Create ticket via API and get the following error

[2022-12-07T12:38:28.254893 #5451-66164940] ERROR – : Missing required value for field ‘abteilung_neu’! (Exceptions::ApplicationModel)
app/models/concerns/checks_core_workflow.rb:62:in block in check_mandatory' app/models/concerns/checks_core_workflow.rb:56:in each_key’
app/models/concerns/checks_core_workflow.rb:56:in check_mandatory' app/models/concerns/checks_core_workflow.rb:34:in validate_workflows’
app/controllers/tickets_controller.rb:165:in block in create' app/models/transaction.rb:17:in block in execute’
app/models/transaction.rb:14:in execute' app/models/transaction.rb:26:in execute’
app/controllers/tickets_controller.rb:85:in create' app/controllers/application_controller/has_download.rb:21:in block (4 levels) in module:HasDownload


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