- Used Zammad version: 3.6.x
- Used Zammad installation source: Docker
- Operating system: Linux
- Browser + version: Firefox or Chrome
Expected behavior:
- Want to use another value on “login” field instead e-mail
Actual behavior:
- The zammad use the same value for e-mail in “login”
Steps to reproduce the behavior:
- It’s the normal behavior
I do this on the database
table: object_manager_attributes
column: name=login
Change the value for
— !ruby/hash:ActiveSupport::HashWithIndifferentAccess
signup: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
“-all-”: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
‘null’: false
invite_agent: !ruby/hash:ActiveSupport::HashWithIndifferentAccess {}
invite_customer: !ruby/hash:ActiveSupport::HashWithIndifferentAccess {}
edit: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
“-all-”: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
‘null’: false
view: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
“-all-”: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
shown: true
But, when i restart the zammad, he back-up to default interface, it’s possible to manage login with different value from e-mail?
Thanks