osTicket - updated review

Some time ago I published a comparison of OTRS and osTicket. I've now had the chance to use osTicket as a daily task management tool, so I thought it might be worth updating my initial impressions.

It has taken a bit to get used to osTicket coming out of a CRM and OTRS as my task management platforms. Specifically, understanding how tickets and tasks relate to one another. The way I've been thinking of it is this:

A ticket is almost like a mini-project - it can be used standalone, with references back to a client creating the ticket and keeping it updated, with tasks (like a work breakdown structure) applied against the ticket. The ticket can't be closed until all the tasks are completed.

Tasks on the other hand, can be autonomous of a ticket and are quick and easy to start, fill in and then to close. There is no link back to a creating user though.

I've used both extensively - many of the tickets I have running have numerous tasks dependent on them (although it is a mutual dependency) and I can farm tasks out to different people to get the job done. In fact, within the work I'm doing now, I've been using OpenProject (which I'll make some notes on soon) to manage the top level project stuff, then breaking the project down into tickets and tasks within osTicket to keep on top of the whole process. It's working pretty well. The project review meetings look at both products and bring it together.

OpenProject isn't great at task management - rudimentary at best, but is great at the higher level project management activities. osTicket isn't good at bigger project work, but handles the lower level complexity very well.

It's important to note too that I have had to migrate osTicket from a XenServer VM to an Azure VM. I simply ran an SQLdump of the whole database and a backup of the install folder (/var/www/html/osticket), set up a brand new osTicket installation, then copied the data I'd backed up across. Restarted the webserver and away we went. I'd like to also point out that I love Let's Encrypt for providing SSL certificates to secure it all.

osTicket reporting is something to be investigated further - the dashboard isn't bad and satisfies my manager that work is getting done, but I'd like to extend it a bit further. Capturing time on tickets is another requirement I need to investigate. These are relatively minor in the current application of this software though and I'm quite pleased by it.

I installed and configured osTicket based on the walk through here:
http://idroot.net/linux/install-osticket-ubuntu-16-04-lts/

It's well worth a look through and I used Digital Ocean's method of applying Let's Encrypt to make it all work as advertised. You can find that link here: https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu-16-04 

Viva la Open Source! A huge shout out to the devs behind these wonderful products and these wonderful walk through pages. We're looking at getting enterprise support for both osTicket and OpenProject to support both. Check them out as alternatives to a paid ticket system and Microsoft Project (and save yourself some real coin!)

Find osTicket here: http://osticket.com/
Find OpenProject here: https://www.openproject.org/

Plone - the open source Content Management System - a review

One of my clients, a non-profit, has a lot of files on it's clients. They need a way to digitally store these files, securely and with availability for certain people. They also need these files to expire and be deleted after a given length of time - usually about 7 years.

These were the parameters I was given to search for a Document Management System (DMS) or more commonly a Content Management System (CMS). There are quite a lot of them, but most are designed for front facing information delivery - that is, to write something, put it up for review, have it reviewed and then published. We do not want this data published ever - and some CMS's make that a bit tricky to manage. So at the end of the day, I looked into several CMS systems that looked like they could be useful.

The first one to be reviewed was OpenKM (www.openkm.com). It looked OK, was open source which is preferable and seemed to have solid security and publishing options. Backing up the database and upgrading OpenKM seemed like a nightmare. I tried a couple of times only to experience great sadness and eventually throwing my hands up in defeat. Scratch that guy off the list.

The next one I seriously considered was Plone (www.plone.org). An open, attractive looking interface certainly helped matters from the get go. I liked it, it looked nice and the decision makers at my client would like it too. Open Source, Linux install - OK good to go. The installation documentation is pretty good, a bit fuzzy at times ( though I do attribute that in part to a lack of solid caffeine) and it was relatively straightforward to get going.

I followed the instructions and started to build the site. It was pretty straightforward and offers different workflow types - so for an internal site, there is no publishing option available. Posts (or uploads of files) are set to either "For Review" or "Private" which is perfect for the application we have at hand here. File size uploads are relatively straightforward to change - there is a config file, much like MediaWiki or similar, that allows for changes to the site that are outside the scope of the in-application setup.

After the build, and setting up internal DNS, outgoing mail and accounts, I set it loose with the client. They have logged in, tested it and come back with a plethora of questions - many many of them. I have changed the security options several times and it's handled it all quite well. Before the system goes into production I'll be making sure backups and restores work. Phone has internal ones that I still need to do more testing on. Stay tuned!