[mylar-dev] issue-tracking repositories proposal

[Eugene Kuleshov <eu@xxxxxxxx>]

  I hope it wouldn't be insulting or obvious, but I'd like to summarize 
existing options for unified issue-tracking infrastructure. There are 3 
Eclipse plugins for Bugzilla and one JIRA plugin (see list in my 
previous email) and each of them has its own nice gems. So, by putting 
all of these gems into one basket we should get a really unique tool.

  In my view there should be 3 major UI elements

-- To register and show repositories we need a Repositories view.
  It can use exact UI as Eclipse-Bugzilla plugin (tree-based widget, 
with root nodes representing repositories).
  I believe that "New Repository" wizard and extension points/api from 
this plugin can be also reused as is. See attached screenshot.png or 
http://people.redhat.com/jpound/bug-systems.png

  Bug repository providers should show at least root node, potentially 
expanding to advanced tree model like one used by Eclipse-Bugzilla plugin.

-- Mylar task list actions should use above repository model/api to 
select single issues or attach queries.

  I see several extension points for these actions (please extend this 
list):

  -- Open issue by id in a special editor or in a web browser
  -- Retrieve info on a single issue by id
  -- Retrieve list of issues for given criteria (should also provide 
optional link for opening in a web browser). Then Mylar should provide a 
wizard where on first panel you can choose provider type (same as "New 
Repository" in above plugin), other panels should allow to select 
provider-specific query and should be contributed by concrete provider's 
plugins.
  -- Create new issue. Mylar should show repository type selection 
dialog and then jump into editor provided by plugin or into web-based UI.


  I'm not sure if there is need to attach one (or multiple?) 
repositories to projects (or perhaps specify bug tracking system for 
each CVS or Subversion repository).
  Anyway there is some UI in Buglist plugin for doing this. See 
screenshot2.png or at 
http://kered.org/project-eclipse_bugzilla_plugin/screenshot2.png

  In our case, for this panel we'll only need a label + Select button. 
On Select it will bring up a dialog that will show list of root elements 
from the repositories view, Ok button and probably Add new button. This 
UI should be similar to "Select Working Set" dialog.

  The only use case for attaching CVS/SVN repositories to 
issue-tracking system I'm aware of - is to provide some link from commit 
comments in CVS or SVN resource history view. Folks from CVS/Team dev 
team may have additional comments. If I'm not mistaken Michael Valenta 
should be in this list.

  regards,
  Eugene


Eugene Kuleshov wrote:
> Mik Kersten wrote:
>
> > Are you subscribed to mylar-dev?  If we're discussing issue-tracking
> > repositories it would be useful to do it there since there was already a
> > bunch of discussion on that topic.
> >  
> Just subscribed. By the way it would make sense to invite few other 
> people. Namely:
>
> Jeff Pound -- http://people.redhat.com/jpound/
> Derek Anderson -- 
> http://kered.org/project-eclipse_bugzilla_plugin/index.html (and anyone 
> from http://groups.yahoo.com/group/buglist/ maillist)
> Peter Nehrer --  
> http://morphine.sourceforge.net/presence/projects/rss/index.html
> Brock Janiczak -- http://jira-dashboard.tigris.org/
>
> By the way it seems that maillist archive at 
> http://dev.eclipse.org/mhonarc/lists/mylar-dev/maillist.html is broken. 
> I don't see anything later then July 25.
>
> regards,
> Eugene
>
>
>
>
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev