https://github.com/clonemeagain/plugin-autocloser

Automatically closes tickets that haven't been updated in a while.

Feel free to propose features in the issue queue.

Features:

- Define a maximum ticket age with no responses.

- Type a friendly message telling your users why their ticket is being auto closed (with full access to ticket variables).

- Let's you choose the start and end states. For instance, if you only want to autoclose tickets in the state Pending, you can.

- Batch the closure of old tickets on a schedule via cron, closes as many or as few at a time as you want.

- Apply filters to only autoclose expired tickets, or tickets that have been answered.

- Can even work with autocron!

Requires zero mods to core.

Built for 1.10.

6 days later

Hello,

Thanks for developing the plugin, I need to know how to see if the plugin is working or some parameter is missing ...

I have configured the plugin to automatically close tickets with the status "Resolved" and change it to "Closed" if 2 days pass, the ticket still does not close.

Is there any way to view the activity logs of the plugin?

It posts to the thread when it changes the status. So you should see that.

However, without seeing how you've configured it I couldn't say more precisely.

The extra logging can be enabled with a small change to the class, I'm thinking of making that an admin setting now. See the readme for details.

If you want to open an issue on GitHub with a screenshot of the plugin config, I'll replicate it on my end and see what's happening.

The most obvious thing to check: is have you enabled the plugin? You can install it and configure it without actually enabling it.

Sorry grizzly, the plugin works fine.I attach the config, I have activated the debug as you indicate in github, however I do not know where to find the debug that are created.

inf plugin.jpg

inf server.jpg

With debug mode on, it should be filling your cron emails with information every time cron runs. Can you post the contents of such a message? It should display the SQL looking for tickets to work on.

Unless you're not getting email when cron outputs text? Try manually running cron from the command line.

I've never used that cron job, and I do not see the option on the admin panel -> general configuration ....However the plugin is working fine, thanks for all grizly; D

Great plugin.Thanks so much.Regards

@[deleted]: you're very welcome, thanks!

@[deleted]: it's part of configuring osticket, setting up cron, http://osticket.com/wiki/POP3/IMAP_Setting_Guide#Schedule_Polling maybe I shouldn't assume that everyone uses it the same way I do.

I have not reviewed this section of the options ... the auto-cron does not have it activated, it is necessary to activate it so that the debugging arrives?

Email Fetching.jpg

Well, it only works via cron, so if you've not configured cron at all, then it won't do anything.

You can use autocron, just tick the box and reduce the number of tickets you want to close each time. Because autocron runs after agent activity.

Done, the auto cron is enabled and config for plugin to.THX for all Grizly 

new plugin config.jpg

12 days later

hi, can we keep the status from "Hold" to "Hold" also & send canned respose. Further, is it possible to have different robot settings for each group.const NUMBER_OF_SETTINGS = 4;

1. I haven't tried that, but give it a go.

2. It's possible to add that, but currently not.

3. Should probably be NUMBER_OF_GROUPS really shouldn't it. One of the two: https://martinfowler.com/bliki/TwoHardThings.html

a year later

Sorry for waking up an old thread but i have some issues with the autocloser.
Setup with 5 groups. Function of changing state is working fine but the problem is that i cannot save a canned respones. (No canned is sent out either)
When choosing a canned respones and save, i got the 'green flag' but after going out and back to the plugin there 'No reply' instead of my canned resp.
On my labsys i did setup it the first time after installing it with the first group only and a canned resp. That's working, but also when trying to add a second group with canned resp that one also go back to no reply.

Server Information
osTicket Version v1.10.4 (035fd0a) — Uppdaterad
Web Server Software Apache
MySQL Version 5.5.42
PHP Version 7.2.10

    rora
    I am not using autocloser, but I think your issue might be due to PHP version 7.2.x (recommended ver. 5.6, I am using 7.0 and so far no issues), which is not supported by osTicket ver. 1.10.4 it may be on 1.11

      3 months later

      Hi @Grizly
      Excelent Plugin. Eager to install over the weekend the upgrade to 1.11
      Will it work on the latest version as well? Or should I wait?
      Keep up the excelent work :-)
      Cheers,
      Paco

      @pakko Hey, unfortunately I haven't tested 1.11 at all yet.. so couldn't say.

      Ah I see. Well when you get around to it will you be so kind to inform us here, please?
      I tought i have turned of the email notification for the cron but it seems not to be the case, get every 2 minutes an email with subject:
      Cron <client@clients-ip> /opt/plesk/php/5.6/bin/php -f 'clients-sundomain/api/cron.php' -- '--user-agent=clients-hash' > /dev/nul. Is the last part wrong?
      Cheers,
      Paco

      9 days later

      Just got my 1.11 Docker environment running, tested, works fine mate.

        3 months later
        14 days later

        Grizly hey i want to ask you a question, can i auto close ticket based on their status example if the ticket is rejected by department Head then the ticket is closed

        P.S : sorry for my bad english ?

            anitasari that's how it works yes, "closed" is really just a status, so essentially it's a "status changing plugin", but that's not what people look for.

                Grizly well when i present the auto close plugin to my employer they said that they want to auto close ticket based on approval status of a ticket like when the user rejects a ticket then the need to be closed immediately or so they say

                  5 months later

                  Hi,
                  Thanks for creating an auto closure plugin it works very well. 

                  I found one issue with this plugin.

                  when status change from resolved to close an auto closure agent (dummy agent) sent mail to the user but in that mail status is still showing resolved not showing closed.

                  Please refer below screen shot.

                    15 days later

                    bDarmesh3 without seeing how you've configured it, hard to say mate, if you post a screenshot of your config to the issues queue of the plugin I'll take a look

                      5 days later
                      18 days later
                      4 months later

                      Hello,
                      Has anyone tested this in 1.12 or 1.14?
                      Also (and excuse this noob's question), is there any plugin repo aside osTicket's (with four plugins) where all other plugins are listed, including versions?

                      Thank you,

                      Mark

                      a year later

                      Is the Ticket Closer plugin still working properly? After saving the configurations to add a canned response for the "Auto-Reply Canned Response" field, it reverts back to "Send No Reply". Also, the plugin automatically closes tickets with pending/open tasks.

                      osTicket Version: v1.12.5 (933bb1f)
                      Web Server Software: Apache/2.4.6 (CentOS)
                      MySQL Version: 5.6.42
                      PHP Version: 5.6.40

                      a month later

                      I already installed Tickets auto closer, and still see many old tickets opened.

                      @Grizly I already installed Tickets auto closer, and still see many old tickets opened.

                      @dontatanka Please reach out to the author of the plugin for support. You would probably want to do that over on the project page. https://github.com/clonemeagain/plugin-autocloser

                      As a disclaimer: While many people do use 3rd Party Plugins (Also called Community Plugins) it is important to know that they have not been evaluated by, are not supported by, are not recommended by, and are not written by the Developers of osTicket. You will need to reach out to the author of the Community Plugin that you are using for support.

                      Write a Reply...