Web App: Juvely

Revision is really boring, and I can’t wait for the exams to be over! As such I have been doing a bit of work on Juvely on and off when I get a chance. I have been working on the user side of things, and I remember we haven’t given you a walkthrough on that yet so I thought I would start off. The basic stuff for viewing and creating tickets is nearly done, but the knowledge base stuff hasn’t been started yet.

The user side is where people who are having problems go. Here is an example below (we probably should note that even though we are using ‘Google’ they are not associated with us or Juvely in any way):

We have gone for a white-box model and will probably keep it this way for all plans (even free ones), other than T&C and copyright notices. The text on the left of the login box are links to various sections. Once you are logged in above the search box we show a list of your tickets and links to other sections:

Next is the submit a ticket page (hmm the title is wrong). The three boxes are for the user to select a priority of the ticket, you can click on the whole box rather than just the radio button to select it. Next to that is the severity slider, this allows a user to select how severe their ticket is. At the moment we haven’t decided on the names of different severities. Under this you can post your ticket and upload files.

Next up you is the ticket view page. At the top is the title of the ticket, on the left is the priority nice and easy to view. Under this are certain details for the ticket. This can be hidden by clicking the hide button (and will stay hidden for the rest of the session) if it gets in the way. Under this is the user’s original message and any attached files.

Under this is the reply and attachment form, and then replies in the same format as in the staff center. Staff replies are shown in yellow and user replies are shown in green.

If you have been following the development you will probably notice that the design for this is completely different to the staff section. James designed this completely from scratch to be as simple as possible, and I guess what he learned while doing the other sections has been put into this. I shall leave it up to him to explain his reasons and what we are going to do about it!