Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On 12/6/06, Scott Ehrlich <scott at mit.edu> wrote: > We have an Access 2000 - created helpdesk program that was designed in-house. > It lives on a Windows 2000 Server with IIS, and uses http as a frontend, cgi > using PERL as a backend. > > The system was put together by COOP students, but I'm not a programmer nor > database person, and the other person with me isn't either. The system is > breaking and it would be nice to know how to manage and fix it ;-) > > The ticketing system needs to be rather basic - auditing per individual user > login; permit simple entry of tickets via the web; provide a history of who did > what; date-stamp activities (ticket open, updates made, date closed, who did > each task); ability to re-open ticket; assigning tickets to another person; for > creating tickets, perform an LDAP query to the organizational-wide LDAP server; > create a report showing closed tickets, for any date range. > > I think that covers many of the basics. > > What are the open source and cheap options for ticketing systems that permit > the above options? It doesn't have to run under Windows. Mantis was chosen by Linux Journal for their 'Editor Choice Awards 2006'. http://www.mantisbt.org/ -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |