OSTicket is not a solution I can use, because I need time tracking also. I never saw a plugin for that for OSTicket.

@JaredBusch said in Upgrading to osTicket 1.11.0: So what is the point of using OSTicket? There are solutions for that. Time tracking would be nice. But lots of shops don't use it. MSPs do, but internal IT often does not.

@Dashrender said in Make an osTicket Database Backup: Total DB Admin noob here - so bare with me. Does this include the username/password setup for this DB? or does that need to be maintained separately? i.e. you have to rebuild from this backup - do you just create a brand new SQL user and grant them rights to this DB upon import, then use that new account to give access to the app? In typing out my question I kinda assume the answer is the second bit - you just create a new user and assign them rights. Correct. The user and the database are separate things.

@bbigford said in osTicket: Basic Ticket Report of All Tickets with Subject: Since there is no inner or outter join specified, inner join is obviously being used where 'join' is specified (outter join having to be explicitly defined where an outter join is needed). How come you explicitly specify 'inner join' at the bottom when you could just use 'join' again as your inner join? Obviously join and inner join accomplish the same thing, just curious why one is not explicitly defined and the other is. I expanded on something done by someone from the osTicket team. it was some weird stylistic choice that they made and I just followed.

We have Spiceworks setup. People email an address we have setup for help. Spiceworks sucks in the email and creates the ticket. Other than when we respond out of it people don't know anything about the ticketing system. You can really change how and when Spiceworks sends out emails, making it almost invisible to the end user. I recommend some type of ticketing system just for tracking purposes.

Oh gosh, I don't even remember.

Not that far into the system yet. I'm looking to move over from SW, but haven't rolled this out for production use.

@sudobashnet said in osTicket 1.10: Hey all, I'm also new here (referred by ntozier via osTicket forums). I'm the developer for the Reports Plugin (the new and improved reporting module for osTicket 1.10). I just wanted to drop in and say hello as well, I'll likely be lurking around anything osTicket related or anything else that catches my fancy while I'm scrolling through. Thanks, Scott Awesome! Great to have you here.

Not a bad idea, the price is good and would make it easy to have a hosted ticket system. I like it.

@black3dynamite Good call. I had to make some adjustments to SELinux.