What I find frustrating about working with aJobs is that it's so hard to maintain context, you'd think that having someone's sheet open, looking at a job and having a conversation in pages wouldn't be an exercise in frustration but it is.
Not to mention when you have several jobs on the same topic (For instance a plot that three different groups of players are working on) you end up having to copy paste the jobs into notepad documents, not ideal.
@Cobaltasaurus
The problem is that a lot of the issues you have with aJobs are things I believeare impossible to fix while still working with MUSHCODE.
For instance take private conversations between staff and a player. On our game all members of staff are Royalty which means they have the SEE_ALL power, this is rather useful when it comes to helping people out with various things however it also means that no matter what sort of locks you put on something, all members of staff can read it by simply get()ing the data directly rather then using +job <x>.
The sensible thing to do I feel is to move the jobs system off the game objects and into the SQL database.
One of the dreams that I've discussed with @Alzie is to take one of the web based ticketing systems like Bugzilla and connect it to the same database as the game. Then players would be able to create and manage their tickets from the game but they'd also be able to get their tickets on their webbrowser/phone etc.