Bug Tracker

[Andy Stone]

Wayne,

That's the thing. I don't think any of this is unique or ground
breaking. Most of what we have in mind has been done before in one
application or another. The problem is that we can't find the solution
that does everything we want. There's always the "deal breaker".

-andy

 

[Andy Stone]

Ahh Kent! Good to hear from you. The first step will definitely be to
look at BugTrack. If you don't mind I would like to run some of the
ideas by you after we have a design for what we are going to build.
Even if BugTrack doesn't match our initial design maybe we can
collaborate and work out a solution? I would really like to be able
to extend BugTrack rather than have two similar projects.

 

[Kent Sibilev]

Sure thing. I was drugged by different projects from the BugTrack
development, but I'm planning to revive it pretty soon.

Cheers,
Kent.

 

[stevetuckner]

Thanks Phil,

As I said with the initial post, I was writing this regardless, but
just wanted to see what had been done with Ruby/Rails that I could
possibly extend. Our feature request is very specific and it's nice
to see the alternatives the other people have mentioned. (Especially
like the subversion interface)

It will definitely have a pluggable architecture as we would like to
include portions of this system into our intranet. We are also
planning on writing an inventory system with ruby/rails that will
integrate with the bug tracker. So, for instance, "john" reports a
bug with some application he has installed. We want the ability to
link (plug into) to the inventory system to see what type of computer
he has, the applications he has installed, etc... This is a very
specific, but beneficial feature that we want and knowing that's not
the norm, we decided to write such a beast. There are a host of other
features that we need and will include.

My plans for setting this up would be to use gems so it would be as
simple as rails.

I'm a big fan of Ruby and would like to see it rule the world.

thanks,
andy

We currently use Instiki for use to track bugs with task pages. What
would be cool, now that Instiki is a rails app (which we haven't moved
to yet), is an integration between Instiki and BugTracker. What I am
thinking of is the ability to have plain wiki pages and also have every
text input also be a wiki "entity". By that I mean that it could be
linked to from other pages. Also it would be nice to be able to link to
objects in the bug tracking system (like Bug #42 or Bug #42-Comment #3
or User:John).

I looked at Trac and it seems to have this capability from my cursory
look at it.

Steve Tuckner

 

[Nicholas Wieland]

- Andy Stone :

We've been looking for an alternative bug tracking system. We were
using Bugzilla, for a long time, but when we opened it up for client
entries we found the interface non-geek friendly. So, we went to
Mantis which is ok, but we had to write some additional modules to get
our base requirements (i.e. LDAP authentication). We never fell in
love with the features of Mantis and missed some of the capabilities
of Bugzilla. So, after looking around for a while the CTO asked if I
would like to write one using Ruby/Rails. I should also mention that
this will be open-sourced. Has anyone started such a project that I
may be able to help with? I will be writing one regardless, just
thought it would be better to ask the group and combine forces rather
than to split up the effort.

I ignore the stage of development of Coterie, but AFAIK it's a TRAC
replacement written in Rails.

http://rubyforge.org/projects/coterie/

HTH,
ngw
--
checking for life_signs in -lKenny... no
Oh my god, make (1) killed Kenny ! You, bastards !

nicholas_wieland-at-yahoo-dot-it
______________________________________________________________________
Yahoo! Mail: 6MB di spazio gratuito, 30MB per i tuoi allegati, l'antivirus, il filtro Anti-spam
http://it.yahoo.com/mail_it/foot/?http://it.mail.yahoo.com/

 

[Dmitri Borodaenko]

We've been looking for an alternative bug tracking system. We were
using Bugzilla, for a long time, but when we opened it up for client
entries we found the interface non-geek friendly. So, we went to
Mantis which is ok, but we had to write some additional modules to get
our base requirements (i.e. LDAP authentication). We never fell in
love with the features of Mantis and missed some of the capabilities
of Bugzilla.

If you know Mantis, you definitely should take a look at ProjectView:

http://www.sam-solutions.net/open-source-solutions-project-view.html
http://www.sam-solutions.net/download/projectview.tar.bz2

I don't think you will use it as it is (it's in PHP, and code is
messy), but you definitely should take a look at it's features list, I
bet you will want to borrow some. It tracks tasks (with dependecies
and gantt charts), bugs, test cases, documents, and work time reports,
and attempts to integrate all that. Haven't seen this combination in
any other open-source project management tool.

 

[Andy Stone]

Thanks Dmitri. And you're probably right. The more references I get
from you guys about systems you like because of the particular
feature(s) it implements the better. I'm sure there are systems out
there that will have implemented something I haven't thought about
that would be really cool to have.

-andy

 

[Andy Stone]

Nicholas,

Thanks for the info. I will definitely look into this project.

-andy