Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

Dashboard Not Showing Stats


I've just freshly installed osTicket.

I have three total test tickets in my system but seeing zeros across the board as far as stats go. Any help would be appreciated.

As you can see from the screenshots. It seems to know there are tickets in the system.

osTicket Versionv1.10-80-gc4669d7 (c4669d7) —  Up to date
Web Server SoftwareApache/2.4.7 (Ubuntu)
MySQL Version5.5.59
PHP Version5.5.9-1ubuntu4.23


  • My understanding is that dashboard stats are a day behind and do not show realtime stats.

  • Well that's a shame
  • That's not the only shame regarding the dashboard imho lol
    It's due for a revamp (or so the rumors are), but when that will happen is a mystery only the devs know.
  • This is one of the reasons why we use @scottro Report plugin [not free].
    www dot software-mods dot com
  • Possibly you need to update to PHP 5.6

    You may also need to apply this PR:

    Fix service & reponse times on dashboard
    git pull origin refs/pull/3738/head

    I thought there was another PR also, however from just a quick look I think I now only apply that one.

    I have a branch on my fork also which adds a little further logging into the dashboard stats. It logs when assignments happen automatically either by auto-assignment or when closing someone else's ticket.

    When this is applied the graphs tend to show equal amounts of "created", "assigned", and then "closed" values.

  • Oh I just wanted to add I think the service time is a little silly. From memory it gives an average between each response.

    So it might take a few hours to initially respond to a ticket, then the client and agents exchange a few messages within a couple of minutes, and based upon how many messages are sent the average service time drops down quickly into the minutes.

    It doesn't really represent anything useful.  Just a plain old service time of time between start to finish would be more useful.

    I could be wrong, that was just from memory when I looked at it.

    The ticket counts are fairly good from what I see however.
Sign In or Register to comment.