[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mylar-dev] interest for issues
|
Thanks Mik. I believe my interest is more related to have results when
element somehow referenced in the report (e.g. in comments, stack
traces, etc) in order to increase visibility of potential conflicts or
similar issues.
Another similar use case could be to include search results from
source control commit log. Though it would require some specialized
server like FishEye.
regards,
Eugene
Mik Kersten wrote:
Yes, we had a prototype quality version of that working and the ideas and
motivation are based on the Hipikat work. I'm hoping that we re-enable it
in the UI not too long after Active Search gets its revamp, tentatively
scheduled for 0.4.10.
The way the prototype worked is that if an element became a landmark the
Bugzilla related elements provider would find all reports that referred to
that element. I used it a bit but not enough to figure out how helpful it
was. What I would like now is an additional provider that finds all reports
that refer to the active one (e.g. via a reference like "bug 123", or an
explicit dependency). There are fancier Hipikat like heuristics that could
be applied to find relevant reports, but that's more of a research problem,
and our current goal is to provide the task context and implicit search
infrastructure that fancier providers to be built on.
Mik
-----Original Message-----
From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
..
Can you please clarify if current active search include bugs/issues
that somehow related to particular landmarks?
I think it would be neat to see know errors/issues for those
landmarks in order to increase awareness about other activities. Is this
something that Hipikat project was trying to do?
_______________________________________________
mylar-dev mailing list
mylar-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylar-dev
