New forum

2018-03-28 Thread Martin Edenhofer
Hello,

we started a new forum for Zammad discussions 3 months ago 
at https://community.zammad.org/

The community there is growing, so we will close this mailing list.

Thanks for understanding,

 -Martin

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/da92814c-5a4c-4af2-913e-0306bf9f4834%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: How to configure elasticsearch

2017-11-20 Thread Martin Edenhofer
kernel_load'
>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:27:in
>>>>>  
>>>>> `run'
>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:360:in
>>>>>  
>>>>> `exec'
>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in
>>>>>  
>>>>> `run'
>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in
>>>>>  
>>>>> `invoke_command'
>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor.rb:369:in
>>>>>  
>>>>> `dispatch'
>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:20:in
>>>>>  
>>>>> `dispatch'
>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/base.rb:444:in
>>>>>  
>>>>> `start'
>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:10:in
>>>>>  
>>>>> `start'
>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/exe/bundle:35:in 
>>>>> `block in '
>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/friendly_errors.rb:121:in
>>>>>  
>>>>> `with_friendly_errors'
>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/exe/bundle:27:in 
>>>>> `'
>>>>> /opt/zammad/bin/bundle:3:in `load'
>>>>> /opt/zammad/bin/bundle:3:in `'
>>>>> Tasks: TOP => searchindex:rebuild
>>>>> (See full trace by running task with --trace)
>>>>>
>>>>>
>>>>> Am Freitag, 17. November 2017 15:32:06 UTC+1 schrieb neoremi:
>>>>>>
>>>>>> Create a test ticket and do this:
>>>>>>
>>>>>> # zammad run rails r "Setting.set('es_url', 'http://localhost:9200')"
>>>>>> # zammad run rails r "Setting.set('es_index', 'zammad')"
>>>>>> # zammad run rake searchindex:rebuild 
>>>>>>
>>>>>> On Friday, November 17, 2017 at 3:54:51 AM UTC-5, Gunnar Maronde 
>>>>>> wrote:
>>>>>>>
>>>>>>> You are right, there was an error. The output is 
>>>>>>>
>>>>>>> drop indexes...
>>>>>>> create indexes...
>>>>>>> rake aborted!
>>>>>>> Unable to process PUT at 
>>>>>>> http://localhost:9200/elrond_zammad_production
>>>>>>> #>>>>>> @data=nil, @code=0, @content_type=nil, @error="#>>>>>> Failed to open TCP connection to localhost:9200 (Connection refused - 
>>>>>>> connect(2) for \"localhost\" port 9200)>">
>>>>>>> /opt/zammad/lib/search_index_backend.rb:62:in `index'
>>>>>>> /opt/zammad/lib/tasks/search_index_es.rake:19:in `block (2 levels) 
>>>>>>> in '
>>>>>>> /opt/zammad/lib/tasks/search_index_es.rake:60:in `block (2 levels) 
>>>>>>> in '
>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.1.0/exe/rake:27:in 
>>>>>>> `'
>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:74:in
>>>>>>>  
>>>>>>> `load'
>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:74:in
>>>>>>>  
>>>>>>> `kernel_load'
>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:27:in
>>>>>>>  
>>>>>>> `run'
>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:360:in
>>>>>>>  
>>>>>>> `exec'
>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in
>>>>>>>  
>>>>>>> `run'
>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in
>>>>>>>  
>>>>>>> `invoke_command'
&

Re: Zammad REST API: How to access ticket history?

2017-11-17 Thread Martin Edenhofer
Hi Martin,

try `GET /api/v1/ticket_history/:ticket_id`

Hope it is what you are looking for.

 -Martin

Am Mittwoch, 15. November 2017 19:03:36 UTC+1 schrieb W. Martin Borgert:
>
> Hi, 
>
> I wonder how to access the history of tickets via the REST API. 
> Esp. I need the information when a ticket has been created, 
> closed, or reopened. 
>
> Thanks in advance! 
>
> Cheers 
>
>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/2bd685b6-12fa-44de-bcb6-2175c349a4fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Failed remote access to Zammad

2017-10-18 Thread Martin Edenhofer
Hi Guilherme,

I access it via http://10.0.0.154

 -Martin


<https://lh3.googleusercontent.com/-qNZuIgoRkr4/WedvCgOht2I/ALc/dbg0cMeR6WcxJnf_FbgepDH9g2am67NFgCLcBGAs/s1600/Screen%2BShot%2B2017-10-18%2Bat%2B17.09.31.png>

Am Mittwoch, 18. Oktober 2017 17:08:17 UTC+2 schrieb Guilherme Corrêa:
>
> Thanks for the reply Martin.
>
> I tried it that way too but it did not work.
> Both with FQDN and IP.
> Could you send me a screen with the correct configuration to compare with 
> mine?
>
> Thank you.
>
>
> Em quarta-feira, 18 de outubro de 2017 13:04:33 UTC-2, Martin Edenhofer 
> escreveu:
>>
>> Hi Guilherme,
>>
>> with nginx you need to configure a ip or fqdn as server_name (without 
>> http prefix). So just replace it with the ip or fqdn which you use in your 
>> browser. 
>>
>>  -Martin
>>
>> Am Mittwoch, 18. Oktober 2017 16:55:19 UTC+2 schrieb Guilherme Corrêa:
>>>
>>> Hello guys,
>>>
>>> How do I configure access to Zammad from other hosts?
>>> I want to access it INTERNALLY at http://support.xyz.com.br for example 
>>> or via an internal ip.
>>> The system will not have public access
>>> Listing this address in the zammad.conf file does not work. I can only 
>>> access it from the local host.
>>>
>>> What can I be doing wrong?
>>>
>>> Ps: This address I'm trying to access does not have any DNS 
>>> configuration.
>>>
>>> My zammad.config looks like this:
>>>
>>> https://user-images.githubusercontent.com/19538568/31722871-fe7c041a-b3fb-11e7-86d3-3878fe47d2b2.png
>>>
>>>
>>> <https://lh3.googleusercontent.com/-J7Oi52TGSv0/WedrO4aP5KI/Dsk/KSylvPp71msrLrl9iSjfpwCEPxcgDg74QCLcBGAs/s1600/31722871-fe7c041a-b3fb-11e7-86d3-3878fe47d2b2.png>
>>>
>>>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/fbe80f4b-04cc-4592-a7d2-187ed19237d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Failed remote access to Zammad

2017-10-18 Thread Martin Edenhofer
Hi Guilherme,

with nginx you need to configure a ip or fqdn as server_name (without http 
prefix). So just replace it with the ip or fqdn which you use in your 
browser. 

 -Martin

Am Mittwoch, 18. Oktober 2017 16:55:19 UTC+2 schrieb Guilherme Corrêa:
>
> Hello guys,
>
> How do I configure access to Zammad from other hosts?
> I want to access it INTERNALLY at http://support.xyz.com.br for example 
> or via an internal ip.
> The system will not have public access
> Listing this address in the zammad.conf file does not work. I can only 
> access it from the local host.
>
> What can I be doing wrong?
>
> Ps: This address I'm trying to access does not have any DNS configuration.
>
> My zammad.config looks like this:
>
> https://user-images.githubusercontent.com/19538568/31722871-fe7c041a-b3fb-11e7-86d3-3878fe47d2b2.png
>
>
> 
>
>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/2daadb88-0040-4998-be6d-98e5e4853a7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Automate Zammad setup

2017-10-10 Thread Martin Edenhofer
Hi Thorsten,

> The auto wizard file seems interesting! How would it be used and what 
settings can it contain?

How to use it:
1) Just install Zammad and start all processes
2) Copy contrib/auto_wizard_example.json to auto_wizard.json and modify it 
as you want
3) Start Zammad via 
http://zammad_host/#getting_started/auto_wizard/:secret_token

-=> All things defined in auto_wizard.json will be created/updated, after 
that will get into Zammad

For all available settings 
see https://github.com/zammad/zammad/blob/develop/db/seeds/settings.rb 

If you want to get your current setting for your Zammad instance (e. g. the 
LDAP config) you can used "zammad run rails r 'p 
Setting.get('ldap_config')'"

Greetings,

 -Martin

Am Dienstag, 10. Oktober 2017 09:44:36 UTC+2 schrieb Thorsten Kaufmann:
>
> Thanks Martin!
>
> To quickly explain my goal:
>
> We are currently evaluating Zammad and i am also evaluating how it could 
> be integrated with our ops standards. We document the way things are 
> supposed to be set up pretty closely and where possible we also
> provide automation and templates (there may be multiple internally hosted 
> instances in different offices for various reasons (e.g. the great firewall 
> and similar)). I'd prefer to provide a template for configuration rather
> than a documentation of what to do in the GUI.
>
> The auto wizard file seems interesting! How would it be used and what 
> settings can it contain?
>
> Cheers,
> Thorsten
>
>
> On Tuesday, October 10, 2017 at 6:11:17 AM UTC+2, Martin Edenhofer wrote:
>>
>> Hello Thorsten,
>>
>> there are different ways for automate deployment. Would be nice to know 
>> your goal.
>>
>> In case there is also a possibility of a auto wizard file 
>> https://github.com/zammad/zammad/blob/develop/contrib/auto_wizard_example.json
>>
>> PS: We started do create a doc page about common commands, 
>> https://docs.zammad.org/en/latest/admin-console.html#example-commands, 
>> feel free to extend it (or ask what you are missing). :-D
>>
>>  -Martin
>>
>> Am Montag, 9. Oktober 2017 17:22:03 UTC+2 schrieb Thorsten Kaufmann:
>>>
>>> Hi there,
>>>
>>> in order to automate deployment of Zammad i was wondering what the 
>>> preferred way of setting up configuration options like the LDAP settings 
>>> and alike.
>>> Via the rails console? Or config file templates?
>>>
>>> Cheers,
>>> Thorsten
>>>
>>> P.S. is there a full command documentation for the console?
>>>
>>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/0497a6d1-b13e-445d-a238-f81ffa43c2d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: cannot find closed tickets

2017-09-21 Thread Martin Edenhofer
Hello Andreas,

it's nice to hear that. 

But back to your question. In a normal agent life, closed tickets are not 
important anymore (because agents are focused on open tickets to get them 
closed). That's the reason why Zammad shows not overview of closed tickets 
per default.

But sure you can find any ticket (if closed or open - it's no matter) via 
the search. So if a customer is sending a followup, the ticket will switch 
to open again (and will be shown to the agents). If a customer is calling 
for a closed ticket, just enter the ticket# or the customer name into the 
search and you also will find closed tickets.

In case you also can create a own overview with tickets closed within the 
last 14 days (but this is really not common).

Greetings,

 -Martin

Am Donnerstag, 21. September 2017 15:50:10 UTC+2 schrieb Andreas Hanny:
>
> Hi to everyone,
>
> we are testing zammad (v2.0.x), after a week we have made some very good 
> experiences with this fine piece of software.
> The only thing we cannot understand is: where can we find the closed 
> tickets? Nothing to find on dashboard/overview or the other screens. Or is 
> this maybe a configuration thing?
>
> Thank you very much!
>
> Andreas
>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/1befdf03-b716-4e92-b803-dfcec8fbc5f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: LDAP integration Community only 50 users?

2017-09-21 Thread Martin Edenhofer
Hi Cengiz,

per default in the admin user list are only last 50 created users are shown.

Just search for it and you will see that you have all users in your system. 
:)

 -Martin

Am Donnerstag, 21. September 2017 12:26:12 UTC+2 schrieb Cengiz Pirasa:
>
> Hi,
>
> I´ve tested the Zammad Community Edition and do have a question.
>
> Is there a limitation with users imported from LDAP?
>
> My last Sync showed me:
>
>
>>- LDAP Benutzer zu Zammad Benutzer (144/144):
>>   - Benutzer: 0 erstellt, 69 aktualisierte, 1 nicht verändert, 74 
>>   übersprungen, 0 fehlgeschlagen, 0 deaktiviert
>>- LDAP Gruppen zu Zammad Rolle Zuweisung:
>>   - Kunde: 0 erstellt, 69 aktualisierte, 1 nicht verändert, 0 
>>   fehlgeschlagen, 0 deaktiviert
>>
>>
> But in the users list there are "only" 50 users.
>
> Maybe a screen/list/print error?
>
>
> Greets!
>
> Btw. Nice Software! 
>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/123081ee-089f-4b01-b0db-aad5e08dd989%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Writing plugin for Zammad for ticket auto-assigning

2017-09-07 Thread Martin Edenhofer
Hi Vishnu,

wonderful usecase! ❤️

By the way, it's also somethin which would fit into Zammad standard.

However, I see 2 features:

1) Auto assignment of Tickets at open time 
2) Auto assignment of Tickets at ticket creation


Where is the best place for:
1) Could be implemented in the UI, if ticket is opened and no owner is 
assigned to auto assignment to the current own.

2) This is quite easy too, if you have the logic how to determine which 
agent will get the ticket assigned. In ruby on rails you can hook into 
callback. In this case for example "before_create" of any ticket.
Here you can put the logic of e. g. round-robin and assign the new agent 
for ticket creation.

Read more at: 
http://guides.rubyonrails.org/v5.0/active_record_callbacks.html

An example in Zammad you can fine 
here: 
https://github.com/zammad/zammad/blob/develop/app/models/observer/ticket/user_ticket_counter.rb#L3
 
or 
https://github.com/zammad/zammad/blob/develop/app/models/observer/ticket/close_time.rb#L31


In case, just fork zammad on github and I can light you the way directly.

 -Martin


Am Donnerstag, 7. September 2017 11:56:32 UTC+2 schrieb Vishnu S:
>
> Hi Martin,
>
> When you have several dozen agents and thousands of tickets coming in, 
> manual ticket claims become very impractical. There may be confusion on 
> what tickets to pick; multiple agents may try to pick the same ticket 
> (there's no locking mechanism); if there are economic incentives, tickets 
> may get hoarded.
>
> The distribution and resolution of tickets will become erratic and uneven.
>
> With automatic assignment, the burden of assignment is not on the agent, 
> but on the system. To start off with, a simple round-robin, or even random 
> assignment of tickets to agents within a group will ensure even 
> distribution.
>
> - Ticket arrives. Filters and triggers are applied.
> - If there's a Group (post filtering), pick a random agent from the group 
> and assign.
>
>
>
>
> On Thursday, 7 September 2017 14:55:38 UTC+5:30, Martin Edenhofer wrote:
>>
>> Hi Vishnu,
>>
>> to give you "good" tip, it would ne nice to know the full usecase from 
>> users perspective.
>>
>> It would also be fine to know hat it the mechanism/rule for  ticket auto 
>> assignment (random?).
>>
>>  -Martin
>>
>> Am Donnerstag, 7. September 2017 11:18:35 UTC+2 schrieb Vishnu S:
>>>
>>> Hi there,
>>>
>>> We'd like to build a simple ticket auto assignment plugin for Zammad. Is 
>>> there any starting point for this? How do we go about writing a plugin?
>>>
>>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/232164c6-8286-40c2-9aa0-f63e966a0dd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Upgrading from 1.5.x to 2.1.1

2017-09-07 Thread Martin Edenhofer
Hi Vishnu,

first of all, I would always recomment to use deb/ubuntu packages as in 
https://docs.zammad.org/en/latest/install-ubuntu.html descriped (this 
packages also includes the needed ruby and gem versions).

The current stable is Zammad 1.5 - so your have installed the package from 
stable repo (as in https://docs.zammad.org/en/latest/install-ubuntu.html 
descriped).

In September we will release Zammad 2.0. If it's release it's show up in 
stable repo as well.

So if you will keep on stable Zammad release you just need to wait until 
new stable releases are relesed. Then just update Zammad via apt and all 
works fine (the package will take care of all dependencies and will execute 
the update procedure).

PS: The Zammad "tag" 2.1.1 is only prepared for "master" branch (which will 
be the upcoming Zammad 2.1 - later). In case, just ignore them and keep on 
stable repo. :)

 -Martin


Am Donnerstag, 7. September 2017 10:08:04 UTC+2 schrieb Vishnu S:
>
> Hi there,
>
> We have installed 1.5.x in production using deb. Now last night, 2.1.1 was 
> released as per https://github.com/zammad/zammad/releases. I'd like to 
> know if theres any safe way to upgrade directly from source to deb 
> installation, also if there are any issues in upgrade. The documentation is 
> a bit confusing and not up to date with latest releases.
>
> Current installation is there in /opt/zammad and we have not done anything 
> apart from whats mentioned in 
> https://docs.zammad.org/en/latest/install-ubuntu.html 
> .
>  
> System is a DigitialOcean instance with ubuntu 16.04
>
> 2.1.1 is in releases https://github.com/zammad/zammad/releases and we're 
> hoping it will have some major updates. Would you suggest us to do it or 
> wait for the deb update? 
>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/5f6c3cf9-b4e2-438c-a48b-a7410f873373%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Zammad vs. autocompletion in search field

2017-08-20 Thread Martin Edenhofer
Wonderful to hear this! :)

 -Martin

Am Sonntag, 20. August 2017 11:12:43 UTC+2 schrieb Lucullio:
>
> Sorry, Martin, the problem occurred after updating another plugin. It had 
> nothing to do with Zammad.  8/
>
> Sorry again and thanks for your help!
>
> Markus  
>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/b2f9e8d4-1edd-4a8d-844c-6a5b61de3fcf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Zammad vs. autocompletion in search field

2017-08-18 Thread Martin Edenhofer
Is it working if you remove the chat widget again?

Maybe I can see then what the difference is...

-Martin

Am Freitag, 18. August 2017 10:40:02 UTC+2 schrieb Lucullio:
>
> Hi Martin!
>
> Not really...
>
> It should be (and it was) like that: If you type at least 3 characters in 
> the search field, you get a pick list of matching products, e.g. typing 
> "baro" should show a list of our Barolo wines.
>
> Since we activated Zammad, all you get in the search field is a 
> "waiting/searching" icon – but no results.
>
> Markus
>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/6ff59402-6629-4d2f-9c31-5f3fbe1b17ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: No Chat window in WordPress

2017-08-11 Thread Martin Edenhofer
Nice! :))

 -Martin

Am Freitag, 11. August 2017 13:58:25 UTC+2 schrieb Lucullio:
>
> Perfekt! 
>
> Vielen Dank, Martin! :))
>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/a9691920-6f82-4a48-b88d-6e78533596cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: No Chat window in WordPress

2017-08-11 Thread Martin Edenhofer
Wonderful!

I the browser console log I see:

<https://lh3.googleusercontent.com/-x8y8VATlKvA/WY2WgZq9arI/AKw/QraIzsvIRCQoQyDufGrGBXBgKSRhp-unACLcBGAs/s1600/Screen%2BShot%2B2017-08-11%2Bat%2B13.32.59.png>

It seems that wordpress is not serving jquery via $. Some lines above in 
your page I found something similar snipped, can you try the following 
snipped?


jQuery(function($){
  new ZammadChat({
background: '#56789b',
fontSize: '12px',
chatId: 1
  });
});


Feedback would be fine!

 -Martin


Am Freitag, 11. August 2017 13:21:33 UTC+2 schrieb Lucullio:
>
> Hi Martin! :)
>
> It's http://lucullio.com
>
> Chat is activated, Agent is online.
>
> Many thanks!
>
> Markus
>  
>
> Am Freitag, 11. August 2017 12:49:49 UTC+2 schrieb Martin Edenhofer:
>>
>> Hello M. ;)
>>
>> the important is, that the Chat-Javascript-Snipped is extecuted after 
>> jquery got loaded.
>>
>> Is there a page available where you added the snipped to check it?
>>
>> PS: By the way, at least one agent need to be available in Zammad Chat to 
>> show the widget.
>>
>>
>> <https://lh3.googleusercontent.com/-ODn3cFoj8qk/WY2LwXo09_I/AKg/nk5GN2pfeJA3Wp_bE7gZeGL_UTSEA95vgCLcBGAs/s1600/Screen%2BShot%2B2017-08-11%2Bat%2B12.49.03.png>
>>
>>
>>  -Martin
>>
>> Am Freitag, 11. August 2017 12:37:13 UTC+2 schrieb Lucullio:
>>>
>>> Hello,
>>>
>>> we are using Zammad with WordPress and Flatsome theme.
>>>
>>> Added the code for Chat integration in "Global settings" > "Footer 
>>> Scripts".
>>>
>>> Unfortunately no Chat window visible.
>>>
>>> Any ideas?
>>>
>>> Many thanks in advance!
>>>
>>> M.
>>>
>>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/069b8245-40fe-408d-9630-c2f26443c0d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: No Chat window in WordPress

2017-08-11 Thread Martin Edenhofer
Hello M. ;)

the important is, that the Chat-Javascript-Snipped is extecuted after 
jquery got loaded.

Is there a page available where you added the snipped to check it?

PS: By the way, at least one agent need to be available in Zammad Chat to 
show the widget.




 -Martin

Am Freitag, 11. August 2017 12:37:13 UTC+2 schrieb Lucullio:
>
> Hello,
>
> we are using Zammad with WordPress and Flatsome theme.
>
> Added the code for Chat integration in "Global settings" > "Footer 
> Scripts".
>
> Unfortunately no Chat window visible.
>
> Any ideas?
>
> Many thanks in advance!
>
> M.
>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/3c1bfacd-0d29-44ce-9eaf-dd349bc9d30d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Zammad Setup and import data from mail account

2017-08-11 Thread Martin Edenhofer
Hi Felix,

would it be an option to just import/fetch all emails via IMAP into Zammad?

 -Martin


Am Donnerstag, 10. August 2017 10:27:37 UTC+2 schrieb FelixFlu:
>
> We plan to use zammad as our new CRM/Helpdesk software and i need to know if 
> there is a way to import
> all our mails into Zammad. 
> Up to now we use the email account of our hoster (all-inkl.com) as kind of 
> CRM/Helpdesk software.
> From what i have read here and in the docs
> i would go for the rest api and write an PHP import script but i am very 
> grateful for every advice
> you can give me and which will save me time. 
> So i have this email account with subfolders for every customer and some more 
> subfolders and i want
> to keep this directory structure. All in all i guess its over 1 mails and 
> some 2000 customers which need 
> to be imported. For old mails i would create one ticket and attach all mails 
> there.
> Does this sound reasonable for you? Any ideas are appreciated.
>
> Thank you very much
>
> FelixFlu
>
>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/1e5199ce-f984-49f3-8518-76340638454b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Error on elasticsearch index creation, no search possible

2017-07-25 Thread Martin Edenhofer
Hi Frank,

I can remember this thread. :)

So normally the default issue is an invalid version of the elasticsearch 
mapper-attachment plugin. To solve this you can check the following:

what is the output of: "/usr/share/elasticsearch/bin/elasticsearch-plugin 
list"

If the plugin is incompatible, follow this steps:

1) systemctl stop elasticsearch
2) /usr/share/elasticsearch/bin/elasticsearch-plugin remove mapper-
attachments
3) /usr/share/elasticsearch/bin/elasticsearch-plugin install mapper-
attachments
4) systemctl start elasticsearch
5) zammad run rake searchindex:rebuild


As far as I can remember, this was not the solution on your side, right?

Other ideas what I have, please let me know what the output of the 
following is:

1) zammad run rails r 'p Setting.get("proxy")'

2) zammad run rails r 'p Setting.get("es_url")'


Greetings,

 -Martin

Am Dienstag, 25. Juli 2017 16:11:40 UTC+2 schrieb Frank Thommen:
>
> Hi, 
>
> I'm am totally at a loss and therefore coming back to this old and still 
> unresolved thread.  I had reported, that we cannot update the 
> elasticsearch index: 
>
> $ zammad run rake searchindex:rebuild --trace 
> ** Invoke searchindex:rebuild (first_time) 
> ** Invoke environment (first_time) 
> ** Execute environment 
> ** Execute searchindex:rebuild 
> ** Execute searchindex:drop 
> drop indexes... 
> ** Execute searchindex:create 
> create indexes... 
> rake aborted! 
> Unable to process PUT at http://127.0.0.1:9200/zammad_production 
> # 
> <http://127.0.0.1:9200/zammad_production#> @success=false, @body=nil, 
> @data=nil, @code="403", @content_type=nil, @error="Client Error: 
> #!"> 
> /opt/zammad/lib/search_index_backend.rb:62:in `index' 
> /opt/zammad/lib/tasks/search_index_es.rake:19:in `block (2 levels) in 
> ' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:248:in 
>
> `block in execute' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:243:in 
>
> `each' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:243:in 
>
> `execute' 
> /opt/zammad/lib/tasks/search_index_es.rake:60:in `block (2 levels) in 
> ' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:248:in 
>
> `block in execute' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:243:in 
>
> `each' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:243:in 
>
> `execute' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:187:in 
>
> `block in invoke_with_call_chain' 
> /opt/zammad/vendor/ruby-2.3.1/lib/ruby/2.3.0/monitor.rb:214:in 
> `mon_synchronize' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:180:in 
>
> `invoke_with_call_chain' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:173:in 
>
> `invoke' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:152:in
>  
>
> `invoke_task' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:108:in
>  
>
> `block (2 levels) in top_level' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:108:in
>  
>
> `each' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:108:in
>  
>
> `block in top_level' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:117:in
>  
>
> `run_with_threads' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:102:in
>  
>
> `top_level' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:80:in
>  
>
> `block in run' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:178:in
>  
>
> `standard_exception_handling' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:77:in
>  
>
> `run' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/exe/rake:27:in 
> `' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/bin/rake:23:in `load' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/bin/rake:23:in `' 
> Tasks: TOP => searchindex:rebuild 
> $ 
>
> elasticsearch otherwise works absolutely fine and I can PUT and GET 
> content via curl locally. 
>
> Martin Edenhofer suggested, that this might be a proxy issue.  However I 
> never consciously configured any proxy settings for zammad, but I had 
> proxies configured in my environment ($http_proxy, $https_proxy) when 
> installing zammad and I had to configure proxies in 
> /etc/default/elasticsearch to be able to install the 
> "mapper-attachments" elasticsearch plugi

Re: required field for tickets

2017-07-16 Thread Martin Edenhofer
Hi Erik,

now I got it. Actually, it's a but. So I created an issue for that:

https://github.com/zammad/zammad/issues/1259

> PS: verdammt geiles System haben Sie da gebaut :) Gruss aus Görlitz :)

Thank you! 鸞

 -Martin


Am Donnerstag, 13. Juli 2017 17:49:32 UTC+2 schrieb Erik Dittert:
>
> oh sorry, you understand me wrong :) 
>
> i want this fields required! so agent should not be able to close the 
> ticket WITHOUT setting this fields. in the ticket view i see a "*" at the 
> field like in the screen. but i can close the ticket also with "null" in 
> the values :)
>
> PS: verdammt geiles System haben Sie da gebaut :) Gruss aus Görlitz :)
>
>
>
> Am Donnerstag, 13. Juli 2017 17:31:03 UTC+2 schrieb Martin Edenhofer:
>>
>> Hi Erik,
>>
>> in the admin interface (where you can define this attributes) you can set 
>> if it's a required field or not.
>>
>> Just select "optional" and you do not need to fill it.
>>
>> Greetings,
>>
>>  -Martin
>>
>>
>> <https://lh3.googleusercontent.com/-nk9nlFTOwtk/WWeSKJUBGwI/AKQ/Qi9USkKd-fsDYeit424lZTjOxmgzdMlmACLcBGAs/s1600/Screen%2BShot%2B2017-07-13%2Bat%2B17.30.15.png>
>>
>>
>>
>> Am Mittwoch, 12. Juli 2017 20:16:12 UTC+2 schrieb Erik Dittert:
>>>
>>> hi,
>>>
>>> i was create some fields... my problem is that i can close the ticket 
>>> without put some values to this "required" fields... why?
>>>
>>>
>>>
>>> Thx!
>>>
>>> Erik
>>>
>>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/a93b52a8-89b4-417f-8f28-f4e0bf73198a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Old tickets not showing

2017-06-21 Thread Martin Edenhofer
嵐 

Am Mittwoch, 21. Juni 2017 14:20:11 UTC+2 schrieb Amir Mofidi:
>
> Thanks Martin!
> That solved it for us.
>
> Den onsdag 21 juni 2017 kl. 10:47:43 UTC+2 skrev Martin Edenhofer:
>>
>> Hi Amir,
>>
>> Zammad is keeping all tickets. Did you install elasticsearch (
>> https://docs.zammad.org/en/latest/install-elasticsearch.html)? In this 
>> case just reindex all objects with "zammad run rake searchindex:rebuild".
>>
>> If you still can't search for all tickets, it seems to be an permission 
>> issue (older tickets could be in a group where you have no access).
>>
>>  -Martin
>>
>> Am Mittwoch, 21. Juni 2017 10:43:25 UTC+2 schrieb Amir Mofidi:
>>>
>>> Hi fellow Zammad users,
>>>
>>> We've set up an installation of Zammad and it's working pretty well. But 
>>> we can not find tickets older that 2 weeks in search or when navigating 
>>> through overviews. 
>>> Does anyone know if tickets are being deleted from database or just 
>>> hidden in the views? Any way keeping all tickets? Because it causes us a 
>>> lot of issues when need to re-open a ticket but it's not there anymore. 
>>>
>>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/32ab26d0-919c-4025-843b-df01d6a037ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Unable to verify sending and receiving for email account

2017-04-17 Thread Martin Edenhofer
Hi Charles,

it should be here: 
https://github.com/zammad/zammad/blob/stable/lib/email_helper/verify.rb#L80

Just increase "9.times" to "25.times" and Zammad will check for 250 seconds 
if the test email arrived in the inbound channel.

-Martin

Am Montag, 17. April 2017 17:53:07 UTC+2 schrieb Charles Shisler:
>
> I went ahead and found the timeout setting, will change on my server, 
> reboot, and let you know how it goes.
>
> On Monday, April 17, 2017 at 8:04:18 AM UTC-7, Charles Shisler wrote:
>>
>> Hey Martin,
>>
>> Yeah I think the IMAP timeout settings could be the culprit. I can see 
>> the email going out via SMTP almost immediately, but it seems like it takes 
>> anywhere from 2-5 minutes for the emails to appear via IMAP on both my 
>> phone and via webmail, which is just enough time for zammad to timeout the 
>> request and return a failure event. Any idea where I could increase this 
>> timeout on my installation so that I could see if increasing it solves the 
>> problem or see if maybe it is another issue? I will also look through the 
>> code myself, I've done a little Ruby on Rails in my time :P Thanks!
>>
>> On Monday, April 17, 2017 at 12:38:16 AM UTC-7, Martin Edenhofer wrote:
>>>
>>> Hi Charles,
>>>
>>> thanks for feedback. One more detail for 3): 
>>>
>>> Zammad is sending an email via outbound channel (SMTP) to inbound 
>>> channel (IMAP) and will watch for this email 45 seconds (this will be done 
>>> 2 times).
>>>
>>> In our tests this 45 sec. was more as enough for all tested email 
>>> provides more as (expecting yahoo - here we discovered sporadically that an 
>>> emails sent to my own mailbox takes up to 10 minutes).
>>>
>>> Any feedback about your scenario would be fine!
>>>
>>>  -Martin
>>>
>>> Am Montag, 17. April 2017 03:27:25 UTC+2 schrieb Charles Shisler:
>>>>
>>>> Thanks for replying.
>>>>
>>>> I can see the multiple emails that are being sent via zammad per 
>>>> attempt. I see them in my Inbox via webmail and using outlook on my 
>>>> iPhone. 
>>>> The emails do see to come a bit slow though. I was thinking it could be a 
>>>> timeout that I need to increase something but I haven't dug too far into 
>>>> the project yet.
>>>>
>>>> On Friday, April 14, 2017 at 12:33:43 AM UTC-7, Martin Edenhofer wrote:
>>>>>
>>>>> Hi Charles,
>>>>>
>>>>> Zammad is doing the following procedure to configure successful an 
>>>>> email account.
>>>>>
>>>>> 1) Verify if incoming (IMAP  or POP3) is working (based on auto 
>>>>> detected settings or on manuell entered settings).
>>>>> 2) Verify if outgoing (SMTP or Sendmail/Postifix) is working (based on 
>>>>> auto detected settings or on manuell entered settings).
>>>>> 3) Sending and email via outgoing channel to incoming channel and 
>>>>> verify if this email arrived in the incoming channel (IMAP/POP3).
>>>>> 4) Try if an external email address is accepted on outgoing channel to 
>>>>> reach external recipients.
>>>>>
>>>>> -=> I guess in your case 3) is failing. Can you try to connect to your 
>>>>> godaddy account via an regular mail client and start the Zammad config 
>>>>> procedure again? Can you see the email of case 3) in the inbox of your 
>>>>> godaddy account?
>>>>>
>>>>> PS: Folder "" and "Inbox" are the same in IMAP (should work with both, 
>>>>> in case just use "").
>>>>>
>>>>>  -Martin
>>>>>
>>>>> Am Donnerstag, 13. April 2017 05:48:14 UTC+2 schrieb Charles Shisler:
>>>>>>
>>>>>> Hello there,
>>>>>>
>>>>>> I have recently installed zammad and look forward to using it for the 
>>>>>> small business I work for. 
>>>>>>
>>>>>> version: 1.4.0
>>>>>> server: ubuntu 16.04x64
>>>>>> install method: apt
>>>>>>
>>>>>> Currently I am having an issue getting email working. I have created 
>>>>>> an email account via my company's godaddy account, and I've entered in 
>>>>>> all 
>>>>>> the correct information regarding IMAP and SMTP. I've made sure that I 
>>>>>> allowed the proper ports in ufw. I've tested the credentials and ports 
>>>>>> seperately on my phone client and had no problem. But when I go to 
>>>>>> verify 
>>>>>> with the self-sent email, it just never succeeds. I've tried with the 
>>>>>> Folder option set to both "" and "Inbox" but it seems to not be able to 
>>>>>> find it.
>>>>>>
>>>>>

-- 
Open Source as Download https://zammad.org || Easy to use as SaaS 
https://zammad.com
--- 
You received this message because you are subscribed to the Google Groups 
"zammad-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to zammad-users+unsubscr...@googlegroups.com.
To post to this group, send email to zammad-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/zammad-users/1c0b9c8d-2538-4813-a846-a71c4ecd49f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.