Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

JIRA vs Bugzilla

1 view
Skip to first unread message

diego

unread,
Jun 13, 2005, 10:49:39 AM6/13/05
to
I want to add in the place I work one tool for trackinig defects.
What do you think about JIRA?? Is it better than bugzilla??
any other recomendation??

Thanks a lot,
Diego.

Message has been deleted

Coolguy

unread,
Jun 13, 2005, 12:25:09 PM6/13/05
to
Tell plz if u have download Url of this

Abraham

unread,
Jun 14, 2005, 11:53:33 AM6/14/05
to
I Have used "mantis", you could try it :-)

http://www.mantisbt.org/

Regards,

Abraham

M.J.L.Builders

unread,
Jun 17, 2005, 11:36:24 PM6/17/05
to
Hi,

I'm a Business Acceptance Test Co-ordinator and my last assignment which was
for a duration of 22 months saw us making a choice between these two
systems.

During this time we attempted to use Bugzilla as our Issues management
System due to our vendor company using it for System testing purposes.

Depending on your need and intended processes and the degree of information
for reporting requirements we found Bugzilla was not suitable as it was
quite limited in it's reporting capabilities in respect of statistics we
were interested in - Severities, Priorities, Areas of Functionality etc.

We then implemented Jira and found that it facilitated our needs a lot
better as long as you had a designated person who was able to
conduct/maintain the configuration needs of the application. The email
alerts and tracking of history events across issues of interest were very
useful and that you could export details to Excel to facilitate sorting and
filtering of the information worked well for us.

In saying that being from the Business Acceptance point of view our needs
were quite specific and also in saying that Jira was the best choice of
these two for us. It however is not the best defect tracking system I have
encountered as I enjoyed the old Rationale SQA Manager the most.

Regards,

Triple_P
"diego" <die...@adinet.com.uy> wrote in message
news:1118674179....@g44g2000cwa.googlegroups.com...

Szymon Kuliński

unread,
Jun 20, 2005, 8:31:05 PM6/20/05
to
I use Scarab -> http://scarab.tigris.org/

Vit

unread,
Jun 24, 2005, 3:40:28 AM6/24/05
to
> I want to add in the place I work one tool for trackinig defects.
> What do you think about JIRA?? Is it better than bugzilla??
> any other recomendation??

After a long study and trial of some similar systems with these two
among them our company has chosen JIRA for itself. But all depends on
what particular services you need...

Vit
http://www.excelsior-usa.com

praveen

unread,
Jun 25, 2005, 3:16:34 PM6/25/05
to
In my opinion, your comparison is not really fair. Bugzilla is a bug
tracking system and a pretty robust one in that. Jira on the other hand
is an issue tracking system. Jira's and other issue-tracking systems
like scarab, etc.., go by the core philosophy that there could be
several different types of artifacts during software development that
need to be tracked. Based on the characterization given to each
artifact using its hooks, an issue could be a bug, an enhancement, a
requirement, a risk, and so on.

Therefore, you would be better off asking yourself whether you want to
track _any_ type of issues including bugs, or just bugs. If your need
is the former, Jira is a very good issue tracking system in that it is
highly configurable. We acquired Jira after evaluating several other
issue tracking systems, including scarab, mantis, and trackplus. Jira
was the winner just because it was slick and portable. The only
downside, if you see it that way, was that it took us 3-4 months to
figure out exactly how we could leverage its flexibility, since it is
so highly extensible.

If you want to simply track bugs, jira is pretty good for that too, and
so are scarab and others already mentioned.

0 new messages