RE: [mylar-dev] interest for issues

["Mik Kersten" <beatmik@xxxxxxx>]

Btw, there's more on this topic in Gail's invited ECOOP paper:

http://www.cs.ubc.ca/~murphy/papers/task/task-structure.pdf

Another thing worth mentioning is that when you work with other tasks now,
the actually do become a part of your task context, and Bugzilla structure
bridge understands the structure of reports down to the comment level.  But
this is not currently exposed in the UI because we're trying to figure out
whether opening a new report should implicitly activate that context since
it's an indication that you're working on it.  This sort of first class
support for tasks and contexts (e.g. relations between them) should start
becoming more prominent later in 0.5.  For the time being we'll add support
for manually copying and pasting contexts, e.g. you start working on a
report, find one that depends on it, then paste the context into the
dependent report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=126237
 
The above discussions should probably be on bug 126327, which reminds me
that it would be useful to have active search for bugzilla reports bring up
any mylar-dev archives that refer to that report!

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Mik Kersten
> Sent: Thursday, February 09, 2006 1:57 PM
> To: 'Mylar developer discussions'
> Subject: RE: [mylar-dev] interest for issues
> 
> 
> 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