I'm considering creating a plugin to add some functionality that I don't believe exists already in osTicket. I'd like to be able to automatically create a task on a ticket if it is transferred from a specific department, to any number of other departments.

Before I dive in a learn how to create plugins for osTicket, I have two questions:

  1. Am I correct in that this functionality does not already exist in osTicket?
  2. If it doesn't exist, are the required Signals available in the plugin API to do what I am looking for?

For example,

  • watch for ticket modification
  • check if it was transferred from "Department X" to wherever.
  • if so, create a task attached to that ticket
  • KevinTheJedi replied to this.

  • tonydew

    1. This does exist it’s just not automatic. An Agent would have to manually create a Task on the Ticket before/after Transferring the Ticket.
    2. Yes, look at the transfer() method for Ticket and you’ll see logEvent() that sends signals for certain actions. Both the core and plugin codebases are fully open source and available on GitHub.

    I will note that we are not accepting any new plugins or features to the current (legacy) osTicket codebases as we are focusing on v2.0 (full codebase rewrite). It’d be highly advisable to clone the osTicket/osTicket-plugins repo and add your plugin within your own fork so you can easily maintain and track issues within your own repo. Just to note, you can't use this forum to advertise nor to report/track issues with your 3rd party mod.

    With all this being said, the legacy codebase will only be around for so much longer (another year or so). The plugin architecture/landscape will be changing dramatically in v2.0 so all existing 3rd party plugins will be virtually obsolete on release.

    Cheers.

      tonydew

      1. This does exist it’s just not automatic. An Agent would have to manually create a Task on the Ticket before/after Transferring the Ticket.
      2. Yes, look at the transfer() method for Ticket and you’ll see logEvent() that sends signals for certain actions. Both the core and plugin codebases are fully open source and available on GitHub.

      I will note that we are not accepting any new plugins or features to the current (legacy) osTicket codebases as we are focusing on v2.0 (full codebase rewrite). It’d be highly advisable to clone the osTicket/osTicket-plugins repo and add your plugin within your own fork so you can easily maintain and track issues within your own repo. Just to note, you can't use this forum to advertise nor to report/track issues with your 3rd party mod.

      With all this being said, the legacy codebase will only be around for so much longer (another year or so). The plugin architecture/landscape will be changing dramatically in v2.0 so all existing 3rd party plugins will be virtually obsolete on release.

      Cheers.

          KevinTheJedi Thank you for the detailed reply. I have no intentions of promoting a third party plugin. Just scratching an itch in our own usage of osTicket. If I am able to create a plugin I would of course have the code available on GitHub, but wouldn't abuse the osTicket forums with advertising / promoting it etc.

          Also, I understand that 2.0 is on the way and I've heard suggestions that the functionality I am after may be part of it. I'm happy to the core application work out of the box if so! There would be no hard feelings about time spent on an old codebase plugin.

            8 days later

            devmansur

            You can always contact us directly via the Contact Us form on our website. As you see in this thread I had already mentioned the non-advertisement above:

            Just to note, you can't use this forum to advertise nor to report/track issues with your 3rd party mod.

            I know we have that Resources page but that was created by the original Forum Admin and all the links are essentially outdated and the linked items do not work anymore. We are leaving it for historical purposes.

            We used to allow people to post about their mods, etc. but they all used to be free and open-source. Now people are charging ridiculous prices for half-baked features/plugins/etc. that's simply not worth it (and most of the time they do not work at all) and is not fit for our open-source product (as our products are FREE). The code is open source so you can do these things however we do not allow it on our own websites anymore. If you want to promote this make your own website and/or repo where you can do such things.

            Cheers.

              Write a Reply...