PDA

View Full Version : problem reporting forum


openbsd-flipp
12-17-2004, 01:31 PM
The company I work for has a small IT department that never really can keep track of the problems let alone pretend to catch up since most of the problems would be resolved if we could install new computers.

So I have come to the conclusion of setting up a problem posting section on our internal webserver. The idea behind this is when people break their computer/printer/other they can post a problem report to this centrilized site for our IT department.

The goal is to have an easy to follow interface(since I do work with a lot of idiots that are easily confuses), a dynamic backend that sorts the problem based on position/servarity of the problem.

The position is a no brainer since the board of directors don't like to be told "you can just ****ing wait untill i get a chance to work on that"{yes, I found that out the hard way but somehow I still have a job}. The servarity is based on how much of what they do is affected by the problem, this will be internally set based on a questioneer the "Human resources" guy sends out to get a feal for the situation. Now comes the question.

What would be a good system to start with? Most of this will be done in php and mySQL but since I am gennerly lazy I do not want to reinvent the wheel to get something that will work.

llbbl
12-19-2004, 10:28 AM
i added paragraphs.

llbbl
12-19-2004, 10:35 AM
What you describe would not be cheap/free to implement. It would require either spending alot of money on a program that is overkill but does a number of things like this. You could hire someone to write a cutomized LAMP application to track things. I would choose the latter.

I think you should suggest that someone with 5-10 years expirence with Linux, Apache, MySQL, PHP (LAMP) be hired for a short project 3-6 months to do this work. That would be the best thing to do.

openbsd-flipp
12-20-2004, 05:48 AM
na I got to thinking that it could be a simple mailto form that gets processed at our end. It all depends on how difficult we want it to be

dang
12-20-2004, 07:20 AM
there are help desk ticketing type systems out there. search freshmeat or sourceforge. Not sure how good any of them are since I've never used one.

llbbl
12-20-2004, 09:23 AM
ok well there you go. Let us know what you find

ECA
12-20-2004, 10:45 AM
The problem will be in PRIORITY..
1. The BOSS
2. Printers, ALWAYS printers, without them you cant PRINT ANYTHING.
3. Computer UPDATES. If a system FAILS, and it isnt updated, its the updates fault.
4. REMOVE ALL FLOPPY drives. There A WASTE of time, and then no one can insert a program from OUTSIDE the company(easily).
5. PASSWORD protect the CD/DVD, so ppl CANT insert own programs and kill system.
6. UPDATE equipment. THIs is LASt, as it costs money, and the BOSS dont want to spend money.

llbbl
12-23-2004, 11:37 AM
ECA that has nothing to do with this ...

http://spams-ukwildcatbasketball.com/Baby.mbe.jpg

ECA
12-23-2004, 12:46 PM
I suggested a priority list...whats the guff, McGRUFF

llbbl
12-23-2004, 02:36 PM
priority list for what man? flipp knows what his priorities are.

llbbl
12-23-2004, 02:38 PM
there are help desk ticketing type systems out there. search freshmeat or sourceforge. Not sure how good any of them are since I've never used one.

You still gotta have someone to install it, customize it for their company and possibly support it in the future. I think flipp is busy enough to take on this task ... but you never know.

ECA
12-23-2004, 03:19 PM
The goal is to have an easy to follow interface(since I do work with a lot of idiots that are easily confuses), a dynamic backend that sorts the problem based on position/servarity of the problem.

FIRST POST...

openbsd-flipp
12-27-2004, 05:54 AM
Over the weekend I was playin arround with "mailto :" <no space> and a filtering shell script. I think that I have been able to get most of the system to work, it is just a few text processing bugs. If anyone is intested I can post the script when I have it finished.

I did look at most of the ticketing software and tat helped mein figuring out what needs to be done but we cannot give the users that many options otherwise if solitare breaks then it will be written up as the whole system is broken.