Bug report, Text field display Error
Hi @deadohr. I guess it’s already reported: Ticket templates creation interface is broken if a Ticket attribute has a lengthy name. · Issue #5000 · zammad/zammad · GitHub
View ArticleAPI Gitlab Ticket Update
Hi, i can’t solved this problem. I watched request headers and i seen bearer token added. If i try to request in Postman, that worked. index.js code; let formData = new FormData();...
View ArticleAPI Gitlab Ticket Update
Not sure I can’t really test it. How can I run it? Maybe the content type is missing? headers: {"Authorization":`Bearer ${bearerToken}`, "Content-Type": "application/json"}
View ArticleAPI Gitlab Ticket Update
You could also try to tail the production log and see if there is a difference between your postman request and your new js request. cd /opt/zammad tail -f log/production.log
View ArticleTable is cut off in ticket
Unfortunately not. I need to create a mail with dummy content
View ArticleTicket reply uses recipient not sender
OK, after some digging and testing I’ve found the solution: I missed one email address that my IT team forgot to mention. You have to enter all the email adresses (Aliases, etc.) related to that...
View ArticleAPI Gitlab Ticket Update
If i added “Content-Type”: “application/json”, error statu changed to 500. Postman send to data with “Content-Type” : “multipart/form-data”. I tried that but not working. It continue the error of CSRF...
View ArticleClik here to view.
Better CSS for .ticket-article-item.system
Sometimes our tickets are monitored by several agents. Internal customer collegues and external users are also notified. Zammad keeps a record of all email notifications for every commentary in the...
View ArticleClik here to view.
Collapsable lists in overviews
Hi, I think Zammad could benefit from making ticket lists in overviews collapsable. Title: Collapsable lists in overviews What is your original issue/pain point you want to solve? Overviews can...
View ArticleIntegrate with GPT
Hello @HeinzSchrot , same requirements here. Zammad usually has got a alrge amount of answered tickets to optimize the answering process. Local LLMs like Ollama (with openAI-API) provide a...
View ArticleClik here to view.
Search for custom ticket fields
Infos: Used Zammad version: 6.2.0-1701867011.fdb4b0b7.jammy Used Zammad installation type: package Operating system: Ubuntu Server 22.0.4 Browser + version: Microsoft Edge 120.0.2210.133 How to search...
View ArticleClik here to view.
Integrate with GPT
We generally do not communicate ETAs and Roadmaps. In fact, this topic is not that much requested. The only feature request I could find that fits this topic has one “like” on the first article....
View ArticleSome pictures not rendering in the ticket
I read that Upcoming Zammad release supports also showing images for html emails. Anyway. We have the semi solution to just download the original formatting and view the html in a browser. So I think...
View ArticleCreate items with API: permission_ids list for roles
Infos: Used Zammad version: 6.2.0-1710170837.6e9cfa61.jammy amd64 Used Zammad installation type: package Operating system: Debian 12 Browser + version: 123.0 (64-bit I’m currently exploring how to...
View ArticleClik here to view.
Some pictures not rendering in the ticket
Nuri: I read that Upcoming Zammad release supports also showing images for html emails. What do you mean? This already is working fine, but not in the way your mail is constructed. I will think about...
View ArticleCreate items with API: permission_ids list for roles
Hi @skip. Permission.find_by(name: 'ticket.agent').id => ID of the permission you could use in the permission_ids array for creating a role.
View ArticleDon't send email when manually creating a ticket
Is is possible that when you manually create a ticket, it does not email the customer with the ticket that was created. We have a number of scenario’s where we create a ticket say due to a back up...
View ArticleCreate items with API: permission_ids list for roles
Thank you for the hint! Using Permission.all.each do |permission| puts "ID: #{permission.id}, Name: #{permission.name}" end I was able to list all permission_ids: ID: 1, Name: admin ID: 2, Name:...
View Article