Problem modifying multiple tickets with customen fields

  • Used Zammad version: 3.0.0
  • Used Zammad installation source: (source, package, …)packages
  • Operating system: Ubuntu 18.04
  • Browser + version: current Firefox & Chrome

In our Zammad-Systen, we have some custome object defined, something like this:

Expected behavior:

  • Now, when I try to modify multiple tickets at once I get this error:
[2019-06-24T15:18:46.167066 #26323-70028872928540]  INFO -- :   Parameters: {"number"=>"20190622710005", "title"=>"PROBLEM - itswww01 - WordPress Updates XXXXX.XXXX is WARNING", "group_id"=>1, "owner_id"=>1, "customer_id"=>79, "state_id"=>"4", "priority_id"=>2, "updated_at"=>"2019-06-22T12:40:05.373Z", "preferences"=>{}, "pending_time"=>nil, "berechnen"=>nil, "projekt"=>nil, "id"=>"3247"}
[2019-06-24T15:18:46.190822 #26323-70028872928540] ERROR -- : Validation failed: Projekt is required but missing. (ActiveRecord::RecordInvalid)

Does anybody have any idea, why it doesn’t work anymore?

I did some furthers tests on this topic.
This problem also occurs in macros.
It seems the main problem is, that the default values for custom objects / attribute isn’t set anymore.


yes, this change is actually (now) working as expected (at least the required part and validation error you get). The issue ( ) earlier was, that after ticket creation Zammad ignored mandatory fields. So frankly, you could simply unset their values without Zammad to stop you from doing so.

With Zammad 3.0 we improved this.
This however will force anything that updates tickets to setthe required fields to any value (if it’s not already set.

As for “my default values are not set” - this seems like a bug, if you’d please fill a bug report on Github, I’d really grateful. :slight_smile:

Thanks for cleary things up :slight_smile:
I just found on Github that there is already a bug-report for my issue (

1 Like

Thanks for the issue, was unable to find it yesterday night :stuck_out_tongue:

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