Issue trackers

[Robert Wohlfarth]

I'm researching issue tracking software for work. There's a lot out there such as BugTraq, Redmine, or FogBugz. With all of the smart, technical people on this list, I was hoping there might be a few recommendations for taking a closer look.

We'll be using the system for tracking data problems (bad formatting, missing information) and file processing. Clients send files, and we load them into a database. When something goes wrong, it often takes weeks to resolve. Remembering everything that has happened is difficult. Issue tracking software would let us quickly see what open issues we have, what has happened, and who is handling it.

--
Robert Wohlfarth

[Greg Donald]

On Thu, Mar 11, 2010 at 12:19 PM, Robert Wohlfarth
<rbwoh...@gmail.com> wrote:
> I'm researching issue tracking software for work. There's a lot out there
> such as BugTraq, Redmine, or FogBugz. With all of the smart, technical
> people on this list, I was hoping there might be a few recommendations for
> taking a closer look.

RT

http://bestpractical.com/rt/

--
Greg Donald
destiney.com | gregdonald.com

[Jim Peterson]

Hello Robert,

You might want to take a look at this site, it has nine different open-source solutions that you can implement on whatever platform your systems are based.

http://www.webresourcesdepot.com/9-free-and-open-source-bug-tracking-softwares/

Our library is too small to use anything like this, but I'm considering it if for no other reason to have a record of what happened when. BugZilla & Mantis are two solutions with which I'm halfway familiar.

Good luck!

Jim Peterson Technology Coordinator Goodnight Memorial Library 203 S. Main St. Franklin, KY  42134 (270) 586-8397 www.gmpl.org Tweet me @GMLGeek Library Technology Blog

--
You received this message because you are subscribed to the Google Groups "NLUG" group.
To post to this group, send email to nlug...@googlegroups.com
To unsubscribe from this group, send email to nlug-talk+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en

[Tim Jackson]

I second RT.... very flexible and robust..

On Mar 11, 2010 12:25 PM, "Greg Donald" <gdo...@gmail.com> wrote:

On Thu, Mar 11, 2010 at 12:19 PM, Robert Wohlfarth
<rbwoh...@gmail.com> wrote:

> I'm researching ...

RT

http://bestpractical.com/rt/


--
Greg Donald
destiney.com | gregdonald.com

--
You received this message because you are subscribed to the Google Groups "NLUG" group.

To post...

[Micheal Swindle]

I like trac.  Very nice and easy to tie a changeset from svn to the ticket.

[Sabuj Pattanayek]

> RT
>
> http://bestpractical.com/rt/

RT is very customizable, but it's difficult to customize unless you're
well versed in the the Perl RT module. One thing I dislike is that by
default there are two interfaces: 1) for regular users which is very
limited, won't even show closed/resolved tickets or allow you to
search for closed resolved tickets (again without heavy modification
to the base RT code) 2) and then another for administrative users
which allows you to look at all tickets, all queues, and pretty much
do whatever you want.

If you need to give users various levels of control on tickets or in
support queues then stay away from RT, unless you have lots of time to
learn the Perl RT module.

If I had to start over I wouldn't choose RT, but again your
requirements may differ.

[Sabuj Pattanayek]

oops, sorry the regular user interface does show closed/resolved
tickets, but you have to setup the search feature on your own.

[Tim Jackson]

FWIW, Jesse and the guys @ Best Practical are very reasonable for
custom development... We spent a little money with them getting us
started with the software, then finished our own customizations based
around what they did...