Re: [sup-talk] Choosing a bug tracker for Sup

From: Dan Falcone <danfalcone@gmail.com>
To: William Morgan <wmorgan-sup@masanjin.net>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Choosing a bug tracker for Sup
Date: Tue, 3 Nov 2009 13:37:22 -0400	[thread overview]
Message-ID: <ed5557340911030937u7f36b4e7p21415f532aac395d@mail.gmail.com> (raw)
In-Reply-To: <1257268977-sup-4810@masanjin.net>

[-- Attachment #1.1: Type: text/plain, Size: 2060 bytes --]

Hi all,

Thought I'd chime in regarding RT.  I've never configured it, but we use it
internally where I work, so I can comment on it from a user perspective.  I
mainly use the email interface, which is very finicky.  If you include
attachments that are too large, RT will ignore your message and will not
attach it to an existing ticket or open a new ticket.  Our instance is well
known to modify attachments (changing the md5sums), which causes all kinds
of problems for us.  Maybe this part is user error, but it also sends 2
copies of every message and doesn't always CC everyone on the ticket when it
is supposed to.  So you either get 2 copies of each email, or zero.  Either
way it sucks. We have lots of processes in place to work around the issues
RT creates for us.  Basically the only reason we use it is for archival
purposes.

Again, I did not install and do not administer this instance, so there could
be configuration issues or possibly newer versions that address these
shortcomings.  However, given my past experience, I wouldn't recommend it.

-Dan

On Tue, Nov 3, 2009 at 1:25 PM, William Morgan <wmorgan-sup@masanjin.net>wrote:

> Reformatted excerpts from Sebastian Schwarz's message of 2009-11-03:
> > Moreover I'd like to advertise/suggest [Roundup][1].  Apart form a slim
> > web interface -- [here][2] Python's issue tracker as an example -- it
> > also offers a fully functional [email interface][3], which allows --
> > from what I understand -- creating, discussing and setting properties
> > like status and labels of issues.
>
> Nicolas suggested this too. I tried installing it locally (late on a
> Sunday night, with a screaming infant in my ear) and couldn't get it to
> behave. But, bugs.python.org looks great, and it looks like they're using
> email to discuss and change issue state, which is awesome. I'll give it
> another shot.
> --
> William <wmorgan-sup@masanjin.net>
> _______________________________________________
> sup-talk mailing list
> sup-talk@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk
>

[-- Attachment #1.2: Type: text/html, Size: 2774 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk