[Rails] ticketing/bugtracking plugin for rails

0 views
Skip to first unread message

Christoph Jasinski

unread,
Nov 13, 2009, 12:21:13 PM11/13/09
to rubyonra...@googlegroups.com
Hi,

I'm looking for a plugin which would enable my rails application to address bugtracking/ticketing similar to lighthouse. The only dependency I can think of is a user model which I would provide. I only need simple stuff like who what where and state of issue. Any suggestions?

Thanks.

Chris

Marnen Laibow-Koser

unread,
Nov 13, 2009, 1:30:05 PM11/13/09
to rubyonra...@googlegroups.com

Have you looked at Redmine?

>
> Thanks.
>
> Chris

Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
--
Posted via http://www.ruby-forum.com/.

Christoph Jasinski

unread,
Nov 13, 2009, 2:35:39 PM11/13/09
to rubyonra...@googlegroups.com
Thanks for the tip, but Redmine seems to be too big for me. I have several little apps in work, so I was thinking maybe there is a plugin that would extend my app with simple, small bug tracking and progress logic. I would suggest that most project are rather little than big e-commerce site. A big standalone bug tracking app is inappropriate in my opinion. When you have alpha or beta testers I don't think they would go to another big website to enter bugs, better leave it on yours.

Maybe I should do a plugin myself. Thanks anyway.

Cheers,
Chris

Joe

unread,
Nov 13, 2009, 2:49:31 PM11/13/09
to Ruby on Rails: Talk
Hi Chris,

I agree with you -- a lite weight way for users to report a problem.

Joe

Aaron Turner

unread,
Nov 13, 2009, 3:07:19 PM11/13/09
to rubyonra...@googlegroups.com
Have you looked at using uservoice.com?

On Fri, Nov 13, 2009 at 11:49 AM, Joe <j...@crimescenechoppers.com> wrote:
>
> Hi Chris,
>
> I agree with you -- a lite weight way for users to report a problem.
>

--
Aaron Turner
http://synfin.net/
http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin
"carpe diem quam minimum credula postero"

Christoph Jasinski

unread,
Nov 13, 2009, 4:38:51 PM11/13/09
to rubyonra...@googlegroups.com
yea, uservoice.com is really cool, but you have to pay to get some nice features (I got some 0 bugs budget projects). It's great for big players, that can effort the payments and can sort of outsource the issue (*don't get me wrong, I like lighthouse etc.). But me and I think a lot of other rails developers have little project and platforms where you don't need such a "big gun" like uservoice.com or redmine.org. In some cases it might be irritating for users or visitors to report problems somewhere else on the internet (not the case with developers). 
In my case, I just start building the app and want to have a kind of a schedule/bugtracking/uservoice/status/... stuff to be there out of the box (through plugin) for me and others (who are not necessary developers). I think it a good way for alpha & beta stages of an app, when people can report directly without leaving the page (which is a little weird for me -- my opinion).

So I think I will have to code it myself. Anyway, that's a nice opportunity to enrich the community (given that the code doesn't smell).

Cheers & thanks
Chris

Marnen Laibow-Koser

unread,
Nov 13, 2009, 4:58:14 PM11/13/09
to rubyonra...@googlegroups.com
Christoph Jasinski wrote:
> Thanks for the tip, but Redmine seems to be too big for me.

Redmine's not big at all.

> I have
> several
> little apps in work, so I was thinking maybe there is a plugin that
> would
> extend my app with simple, small bug tracking and progress logic.

This is best done as a separate application, I think.

> I
> would
> suggest that most project are rather little than big e-commerce site.

Agreed.

> A
> big
> standalone bug tracking app is inappropriate in my opinion. When you
> have
> alpha or beta testers I don't think they would go to another big website
> to
> enter bugs, better leave it on yours.

Nope. Redmine isn't "big", and it's entirely appropriate to expect your
testers to go to a separate bug tracker. If branding and usability are
concerns, you can install it on the same domain and provide a link in
your app. But keep it separate -- don't pollute your app with a bug
tracker.

>
> Maybe I should do a plugin myself. Thanks anyway.

Maybe you should just use a separate tracker! :)

>
> Cheers,

Matt Jones

unread,
Nov 14, 2009, 12:14:13 PM11/14/09
to Ruby on Rails: Talk


On Nov 13, 4:38 pm, Christoph Jasinski
<christoph.jasin...@googlemail.com> wrote:
>
> So I think I will have to code it myself. Anyway, that's a nice opportunity
> to enrich the community (given that the code doesn't smell).

One nice thing about the external bug trackers: you can report things
like "the website is down". Hard to do that if the site is hosting the
bug tracker...

--Matt Jones
Reply all
Reply to author
Forward
0 new messages