1) Is there a demo site ?There is no demo site per se. The hosted version runs on a slightly different version of osTicket than you can download but only in that they have some additional control panels for their users. It's close enough where you could compare the two and get a fairly meaningful comparison. There is of course no replacement for setting up your own test site.2) Is there a limit to the number of techs that can use the download version? Are there any limitations (for anything)?There is "no limit" to the number of Agents (techs) who can use the download version. There is "no limit" to the number of Users (clients) either. That being said the id field on both tables is a 10 or 11 digit number. So technically there is a limit, but it could be over come. There is also the matter that DB and website performance would probably be an issue the larger the numbers, but you can scale your servers. Also MySQL technically has limits on table size based on host OS.There is a limit to the number of tickets a user can have open at once, but thats a admin set number.3) Can osTicket handle or be set up for multiple domain / branding support from a single installation ?This is not a feature at this time. It could be done. But it would be far from perfect. I know that this is on the to do list that the devs have.4) If it does not support multiple domain / branding, is it possible to
configure different organizations as "departments" and assign access to
only their "department" so they can not see other departments ? And is
it possibly to create sub departments ?Yes. :)5) Name me some of the problems and complications you have run into with
osTicket. Possibly things you think should have been in it and are just
missing and make it harder for you to do your jobs. Or some of the "oh
by the way" issues that have caught you off guard ?So this part of my reply isn't exactly a caught off guard sort of thing. It's a list of things that I feel are important and my feelings on some of them. A. You really need to run cron.php (using taskscheduler or cron), even if you think you don't need to... you should.B. The reporting in osTicket (Dashboard) is beyond bad. Luckily there is a reporting mod that is excellent written by a forum member @[deleted] C. The LDAP features while functional leave a little to be desired (such as populating additional data points, etc). Luckily there is an LDAP mod written by forum moderator @[deleted] that can be run that imports extra data, etc.D. The devs are not very publicly active on the forums. While one can open issue reports on github and get to them more directly the forum community is mostly run by the forum moderators and members. Personally I would rather have the devs doing things like being devs so this is okay... but people rarely want to deal with customer support when they think they could just talk to a dev to fix their mission critical bugs.E. There are some features I feel are lacking. I have written blog posts on how to implement some of them, and released the vast majority of my mods to the public. Other people have done the same. There is generally no time line available to the public for when features will be implemented. The devs do a pretty good job of keeping me in the loop and I try to relay information and answer questions as do others.IF you have any more specific questions please do not hesitate to ask. :)
