Creating a ticket and new user with API & request header X-On-Behalf-Of
Hi @inevitable. In my opinion, you’re mixing up stuff here. On behalf of and customer are two different matters…
View ArticleHTML document for app
Maybe this could be interesting: app/assets/stylesheets/custom/README.txt But keep in mind, after very update of Zammad this could be broken and also I think the file needs to be re-added.
View ArticleMobile App Email Answer modify
Hello @nikomax I can confirm that there is currently a problem on mobile devices, but I think it’s related to the editor we are using (we will check if there is already a related bug). As a...
View ArticleEmail ticket doesn't work when Storage Mechanism is changed to S3
Hi @inevitable. Could you please share some excerpts of your production.log file when the ticket creation fails?
View ArticleIssue with API token permissions ticket.agent
It’s correct that you can use the User-Endpoints with ticket.agent permission (because you are allowed to handle customer users and also see other users). But there should be currently some...
View ArticleEmail ticket doesn't work when Storage Mechanism is changed to S3
Did you really restart all the services after you switched the storage provider?
View ArticleEmail ticket doesn't work when Storage Mechanism is changed to S3
Yes. And somehow, creating tickets via API(Postman or custom Form tested) worked. Strangely, everything works great except making the tickets with mail. As I said, after changing to DB, Zammad can...
View ArticleEmail ticket doesn't work when Storage Mechanism is changed to S3
API and Form are working with the Webserver and the Email-Handling is working with the Background-Worker, so this could be the difference. But yes, in the end when the complete email handling is no...
View ArticleCreating a ticket and new user with API & request header X-On-Behalf-Of
I know that’s not the same thing. I thought that on HTTP Request X-On-Behalf-Of(not empty) and function “guess”, Ruby can check the email and, if does not exist, create a new user. If the header is...
View ArticleClik here to view.
Email ticket doesn't work when Storage Mechanism is changed to S3
dominikklein: Are the emails afterward in the unprocessable-mail folder? Nope. I tracked and saw the incoming emails, and they quickly vanished because of Zammad’s Email conf not to keep emails in the...
View ArticleEmail ticket doesn't work when Storage Mechanism is changed to S3
I mean on Zammad side, normally when the mail handling fails, they are moved to the var/spool/unprocessable_mail folder.
View ArticleClik here to view.
Filters for web channel
The question is what is your problem which you want to solve? E.g. the customer can already select a group in the web form. Or do you want to pre-fill this field because of some other selection? Then...
View ArticleEmail ticket doesn't work when Storage Mechanism is changed to S3
I tried now, and there’s the unprocessed emails: zammad@a7f54cac6be2:~$ ls var/spool/unprocessable_mail/ 540f8fcda385a50a179ab41de767762e.eml 6ea565e099df8c1bcd9c92b93dbba2c8.eml
View ArticleEmail ticket doesn't work when Storage Mechanism is changed to S3
I succeed with Rails command Channel::EmailParsers.process_unprocessable_mails Also, I see the attachments on the S3 bucket from now processed emails. Interestingly, it seems to be an issue with the...
View ArticleClik here to view.
Cannot Modify Triggers
Infos: Used Zammad version: version 6.2.0-1702975436.87754a02.jammy Used Zammad installation type: package Operating system: Ubuntu 22.04.3 LTS x86_64 Browser + version: Chrome Versión 120.0.6099.129...
View ArticleRestore data with new version
You need to provide user & db. Try with this: psql -U zammad -d zammad_production
View ArticleRestore data with new version
yes! it’s working. and for my main request, do you have any ideas?
View ArticleClik here to view.
Restore data with new version
Ours: /var/lib/docker/volumes/zammad-docker-compose_zammad-data/_data/ As I can see, this is the old tutorial with Zammad 4.0 version, so I assume you can’t have that volume. Did you try first to...
View ArticleOTRS 6 CE Migration: Validation failed: Name contains invalid path...
Could be that with the new group hierarchy feature, the import has some problems, when the queues are not imported in the correct order (maybe a parent group is missing). The current exception has no...
View Article