We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
6.1
cat /etc/os-release
E, [2023-09-22T16:24:51.345929#32187-5700] ERROR -- : Error performing Core Workflow engine. E, [2023-09-22T16:24:51.345981#32187-5700] ERROR -- : undefined method `id' for nil:NilClass user.group_access?(record.group.id, access) ^^^ (NoMethodError) app/policies/ticket_policy.rb:87:in `agent_access?' app/policies/ticket_policy.rb:57:in `agent_update_access?' app/models/core_workflow/custom/ticket_time_accounting_check.rb:21:in `available_for_user?' app/models/core_workflow/custom/ticket_time_accounting_check.rb:17:in `enabled?' app/models/core_workflow/custom/ticket_time_accounting_check.rb:5:in `saved_attribute_match?' app/models/core_workflow/condition/match_all_modules.rb:13:in `block (2 levels) in match' app/models/core_workflow/condition/match_all_modules.rb:10:in `each'
No errors
Select empty group on support instance.
No response
yes
The text was updated successfully, but these errors were encountered:
TicketPolicy.new(current_user, selected).agent_update_access? should be done the with saved ticket.
TicketPolicy.new(current_user, selected).agent_update_access?
zammad/app/models/core_workflow/custom/ticket_time_accounting_check.rb
Line 21 in 5b6ad99
Sorry, something went wrong.
242e0f7
Fixes #4835 - Time accounting check crashing when no group is selected.
d797cc9
rolfschmidt
dominikklein
No branches or pull requests
Used Zammad Version
6.1
Environment
cat /etc/os-release
): [e.g. debian 10.4, ubuntu 20.04]Actual behaviour
Expected behaviour
No errors
Steps to reproduce the behaviour
Select empty group on support instance.
Support Ticket
No response
I'm sure this is a bug and no feature request or a general question.
yes
The text was updated successfully, but these errors were encountered: