Easy - don't stress. Just look at is as "job security." In our current day, that's a much more important factor than in the past. Otherwise, do prioritize, and document - documentation is really helpful in so many ways we can't even imagine. Here's a few:
1. Record for you - if you record the issue, who requested, and in the end, how you resolved, it'll give you a historical record. When the same issue is brought up in the future, you'll be able to look back and say, hey, this is what worked the last time. Also, if you have a problem user, you'll have documentation to back-up any complaints you might need to make to management IF and when necessary.
2. Record for your boss - "Yeah, I've been working, and here's what I've done."
Well, not the best organization here, but it's there. If the company will put up the money for it, a "help desk" type software would be good.
One fairly quick and easy method you could do yourself, assuming no hiccups along the way, and for free, would be to set up a Drupal based website (
and install the Storm module, along with any required modules for it - it'll tell you if something is required. It's a project-management suite built into a web application. So, if you have a server on which you can run Linux (it may run on Windows, but I'm not sure), then you could install this... then again, since you've never used it, you especially don't have the time.
Well, use the ticket system if possible - email, whatever... you could take the emails, for now, and just stick them in a folder either in your file system, or within your email application... maybe have a "to do" folder, and a "done" folder, rather than just delete... then when things are more calm, you could go back and build a history off of that..
Okay, no more rambling from me this morning..
![[wink] [wink] [wink]](/data/assets/smilies/wink.gif)