Mantas Masalskis

> Nah I'm good thank you ... wrong dk most probably, though 🤣 Oh crap… Sorry dude. Thank you for pointing it out 😁

@mgruner Yes. That's why I added `specification required` label. Edited to be more clear. ping the real @dominikklein :)

This is a very interesting issue. The new data is escaped (see https://github.com/zammad/zammad/blob/f7fde26feaf3f96768f92fc3c3f3daf6f7f67c9b/app/models/concerns/perform_changes/action/attribute_updates.rb#L123) when assigning. However, ticket title is always escaped too. This causes special characters to be double-escaped. The...

I am also confused by relation of this and #5099. There's a bug as per #5099, but then this is non-issue. On the other hand, I could see why someone...

@kylebial0 looks like your API returns `false` where you try to provide a key deeper into a nested hash. I've a feeling this may be a misconfiguration rather than an...

@kylebial0 hmm. Above screenshot says Search result list key is named `device`, but there's no such key in your JSON? Although it shouldn't crash with a `dig` error even then...

Looks like `Digit required` has `tag: select` while it should be `tag: boolean`?

I'm not sure if this is a bug. It's by design. The setting is used to toggle on/off admin UI features if an active KB exists.

Those settings are used to push state to UI wether there's an active (public) KB. Meanwhile knowledge base's active flag is the main source of truth. Sorry if this is...

I know. Right now it works only one way. changes in KB update `kb_active` and `kb_active_publicly`. It does not work the other way. My train-of-thoughts was that I wasn't sure...