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.
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. 😉