Hey all - I noticed that when a task becomes overdue on our osTicket instance, it doesn't send a Overdue alert. However, an alert is sent for an overdue ticket.
I have enabled alerts and set it to send it to the assigned agent for that task, under task settings:

Any ideas? Cron is working fine, and I can't see any logs suggesting that anything is failing. Maybe it's a really simple checkbox that I need to tick... I've had a look around and can't see anything.

The reason for wanting this is that I also use osTicket for projects as well as tickets, and a 'Project Ticket' will have several tasks, assigned to different agents. It's ideal to have an alert when one is overdue.

Please see environment details here:

Not that I think it is causing your issue, but you are running an unsupported webserver software (LiteSpeed).

I do not use Tasks so I haven't really played with these settings, but it looks pretty straight forward and it looks like you did it right.

Does your Default Alerts Email configured have an SMTP server configured? (this would be in Admin panel -> Emails -> Emails -> your alert email. Note your Default Alert Email is configured at Admin panel -> Emails -> Settings)

Hey - thank you for your response. Really grateful btw for your ongoing assistance in this forum - your responses are always very helpful!
I didn't realise that LiteSpeed wasn't supported! I am running osTicket on a shared hosting platform, installed via Softaculous. Other than this issue I reported above, I haven't had any other issues. However if I do then I will probably migrate it to its own dedicated server/VPS with IIS or something.

I just checked, the alerts e-mail hasn't been setup, no! Thanks for that recommendation, I wouldn't have even thought to look there! I will set this up now and let you know how I get on! Once again - really grateful for your help and support, thank you.

So upon testing, I still get the 'Task Assigned to You' e-mail, but not the overdue one. I set the due date to about 4 minutes ago, and no e-mail. However the ticket that was also overdue did send a message!

I rarely use tasks, but they're really useful for 'nesting' almost like a mini ticket within a ticket, which is great when we do projects that utilise multiple resources for one project - if that makes sense?!

It's not a big issue for us as I don't use this often. Just seemed like a useful feature to have working. I can grab the info from a Power BI report or something instead!

Absolutely adore the software otherwise!! Completely redesigned my business with it. Basically integrated the DB tables within osTicket with everything else we use. Don't think I could ever go without it now 😃 !!

@adamjrberry

The Overdue Task Notifications never worked (ever). It was more of a placeholder as it was a direct copy/paste from the Ticket notifications. This will eventually be revisited and the functionality will eventually be added.

Cheers.

    @KevinTheJedi
    Fantastic thank you for confirming! That'll explain it 🙂 . Thanks for your support. Have a good weekend.

    18 days later

    KevinTheJedi Hi Kevin, in regards to the "Overdue Task Notifications" do you currently know the timeline around when this with be implemented, the reason i ask is we really need this functionality asap.

    Regards, Tony

      The devs do not generally give answers to questions like "when will X feature be done?" or ""when will Y version be released?" If you need this functionality asap then you would need to either roll your own code changes to get it working, or likely hire a freelancer to do the development of that feature.

      @Rambo64

      We do not have set release dates for really anything as development is very unpredictable. With this being said we are focusing most of our efforts in the new v2.0 codebase (full codebase rewrite). I would imagine we would implement this after that version is released and stabilized (which we have no set release date for as well).

      Cheers.

      5 months later

      I spent a good bit of time troubleshooting this only to discover now that it's a feature that doesn't actually work. Options for it should be removed, until it actually exists.

      Write a Reply...