Academic Research: Recommending similar bugs

[H. Rocha]

Hello,

I am a PhD student at UFMG, Brazil. As part of my research, I am working
with a recommender for similar bugs.

The idea is to recommend to a developer who has fixed or is working on a
bug X that there are similar bugs X1, X2, etc in the tracking system.
Currently, I am assuming that two bugs are similar if they are assigned to
the same component and share some similarities among their textual
descriptions.

In fact, we implemented a prototype extension of Bugzilla, with recommendations
of similar bugs, called NextBug. We also have some results showing that
similar bugs happen in real systems. Finally, we conducted a small survey
with Mozilla developers, who also provided an interesting feedback.

Therefore, if possible, I would like to discuss with Bugzilla's developers
if they seem such recommendations useful and if they have interest on
including a similar feature in the system.

I appreciate any comments on the matter.

Thank you in advance for your collaboration.

- Henrique Rocha
Computer Science PhD Student
Applied Software Engineering Research Group (
http://aserg.labsoft.dcc.ufmg.br/)

[Mike Hoye]

Post by H. Rocha
In fact, we implemented a prototype extension of Bugzilla, with recommendations
of similar bugs, called NextBug. We also have some results showing that
similar bugs happen in real systems. Finally, we conducted a small survey
with Mozilla developers, who also provided an interesting feedback.
Therefore, if possible, I would like to discuss with Bugzilla's developers
if they seem such recommendations useful and if they have interest on
including a similar feature in the system.

Certainly as a community manager I'm interested - the prospect of
automating, even partially, a next-good-bug search is pretty compelling
from a community-building and contributor-fostering sense.

- mhoye
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla-CzyLcWPZiU5YsZ3hbOqMTti2O/***@public.gmane.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=gcbd-developers-Uylq5CNFT+***@public.gmane.org>

[Andre Klapper]

Post by H. Rocha
The idea is to recommend to a developer who has fixed or is working on a
bug X that there are similar bugs X1, X2, etc in the tracking system.
Currently, I am assuming that two bugs are similar if they are assigned to
the same component and share some similarities among their textual
descriptions.

I highly appreciate when academia reaches out to developers.
There seems to be a huge gap between research and getting stuff
implemented upstream.
There's been dozens of research papers (and some prototypes) on
duplicate detection in Bugzilla and I assume you're well aware of them.


Still I'm very curious:

So your basic assumption is that tickets are triaged and end up in the
correct component? That sounds very similar to Sun et al.'s "Towards
More Accurate Retrieval of Duplicate Bug Reports" at
http://www.comp.nus.edu.sg/~specmine/suncn/papers/ase11.pdf

Did you consider using additional contextual word lists (like Alipour,
Hindle and Stroulia in "A contextual approach towards more accurate
duplicate bug report detection")?

Did you consider giving tickets created in a similar time span more
weight (Prifti, Banerjee and Cukic did that in "Detecting bug duplicate
reports through local references")?

Did you consider giving higher exposure to reports which have a high
number of comments as they likely also receive more duplicates
(Cavalcanti et al. tried that in "The bug report duplication problem: an
exploratory study")?
(All three papers don't have some public access that I'm aware of.)

In any case, that's probably all stuff to only consider once some basic
code actually HAS landed in upstream code.

andre
--
Andre Klapper | ak-47-***@public.gmane.org
http://blogs.gnome.org/aklapper/

_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla-CzyLcWPZiU5YsZ3hbOqMTti2O/***@public.gmane.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=gcbd-developers-Uylq5CNFT+***@public.gmane.org>

[Gervase Markham]

Hi Henrique,

Post by H. Rocha
In fact, we implemented a prototype extension of Bugzilla,
with recommendations of similar bugs, called NextBug. We also have some
results showing that similar bugs happen in real systems. Finally, we
conducted a small survey with Mozilla developers, who also provided an
interesting feedback.

Is the code for this extension available anywhere?

Post by H. Rocha
Therefore, if possible, I would like to discuss with
Bugzilla's developers if they seem such recommendations useful and if
they have interest on including a similar feature in the system.

I think it would be good for us to see and evaluate your prototype.

Gerv

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=gcbd-developers-Uylq5CNFT+***@public.gmane.org>

[H. Rocha]

Hello all,

Thank you very much for the feedback. I welcome any comment on this subject.

Post by Mike Hoye
Certainly as a community manager I'm interested -
the prospect of automating, even partially, a
next-good-bug search is pretty compelling from a
community-building and contributor-fostering sense.

I hope NextBug could help with that. The experiments show reasonable
results so far.

Post by Mike Hoye
I highly appreciate when academia reaches out to developers.
There seems to be a huge gap between research and getting stuff
implemented upstream.

My research group also shares these believes. We are always trying to apply
our research to help developers.

Post by Mike Hoye
There's been dozens of research papers (and some prototypes) on
duplicate detection in Bugzilla and I assume you're well aware of them.

I am aware of the papers you mentioned and I am considering theses works to
improve our current prototype.

Basically, our current prototype is indeed more similar to Sun et al. (2011)

Post by Mike Hoye
Is the code for this extension available anywhere?
I think it would be good for us to see and evaluate your prototype.

Yes, we have a prototype tool already running. Please look at: <
http://aserg.labsoft.dcc.ufmg.br/nextbug/ >

Of course, we are working hardly now to improve this first prototype. In
fact, by next week we plan to have a new version where the developers can
customize filters to select recommendations on just specific types of bugs
(e.g, bugs of a certain severity, bugs not assigned to anyone, etc).

Thanks again for all the comments.

- Henrique Rocha
Computer Science PhD Student
Applied Software Engineering Research Group (
http://aserg.labsoft.dcc.ufmg.br/)

[Gervase Markham]

Hi Henrique,

Post by H. Rocha
Yes, we have a prototype tool already running. Please look at: <
http://aserg.labsoft.dcc.ufmg.br/nextbug/ >
Of course, we are working hardly now to improve this first prototype. In
fact, by next week we plan to have a new version where the developers can
customize filters to select recommendations on just specific types of bugs
(e.g, bugs of a certain severity, bugs not assigned to anyone, etc).

A few ideas and suggestions:

* You should make your tool a proper Bugzilla Extension:
http://www.bugzilla.org/docs/tip/en/html/api/Bugzilla/Extension.html

There is a template hook called "after_custom_fields" which would be
perfect for you to add your new UI to the bug edit screen. This would
mean your extension would work with more than one version of Bugzilla.

* You should use Template Toolkit and the template system to produce
any HTML you need, rather than using print() statements as now.

* Instead of loading the data via jquery, you could use code hooks to
prepare it when a page was being viewed, and then just access it
directly through template variables in the edit.html.tmpl template.

The general idea of your tool looks great, though :-)

Gerv
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla-CzyLcWPZiU5YsZ3hbOqMTti2O/***@public.gmane.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=gcbd-developers-Uylq5CNFT+***@public.gmane.org>