Difference between revisions of "Mylyn/SOC/2006/Bugzilla Connector Enhancements"

From Eclipsepedia

< Mylyn‎ | SOC
Jump to: navigation, search
m
Line 1: Line 1:
 
'''Phase A:''' ''Bridging the Gap''
 
'''Phase A:''' ''Bridging the Gap''
 
   Mylar's expanding user base in the eclipse community is quickly making it a standard choice for eclipse integrated bug tracking.  
 
   Mylar's expanding user base in the eclipse community is quickly making it a standard choice for eclipse integrated bug tracking.  
   It is not the only choice however, eclipse-bugzilla (a former project of mine) provides similar functionality for bug tracking. There
+
   It is not the only choice however, eclipse-bugzilla (a former project of mine) provides similar functionality for bug tracking.  
   has been ongoing discussions on merging the two projects, but no action has been taken yet. Thus, the first phase of this project
+
   There has been ongoing discussions on merging the two projects, but no action has been taken yet. Thus, the first phase of this  
   will focus on bringing functionality from eclipse-bugzilla to Mylar. This list includes:
+
   project will focus on bringing functionality from eclipse-bugzilla to Mylar. This list includes:
 
   - Support for bugzilla collections as query options
 
   - Support for bugzilla collections as query options
 
     * Collections are a new feature of bugzilla which allows products to be grouped
 
     * Collections are a new feature of bugzilla which allows products to be grouped
Line 30: Line 30:
 
'''Phase B:''' ''Full Feature Editing''
 
'''Phase B:''' ''Full Feature Editing''
 
   Mylar's bug editor provides a structured approach to composing comments for bug reports. In its current form it lacks full support  
 
   Mylar's bug editor provides a structured approach to composing comments for bug reports. In its current form it lacks full support  
   for bugzilla features. This phase of the project will focus on adding editor support for missing bugzilla features with high quality
+
   for bugzilla features. This phase of the project will focus on adding editor support for missing bugzilla features with high  
   integration into the platform. These features include:
+
   quality integration into the platform. These features include:
 
   - Adding attachments
 
   - Adding attachments
 
   - CC list management/selection
 
   - CC list management/selection
Line 46: Line 46:
  
 
'''Phase C:''' ''Researching and Prototyping Future Editing Features''
 
'''Phase C:''' ''Researching and Prototyping Future Editing Features''
   Task repositories are beginning to support a richer editing via a wiki style syntax (eg. JIRA). In addition, wikis in general are becoming
+
   Task repositories are beginning to support a richer editing via a wiki style syntax (eg. JIRA). In addition, wikis in general are  
   a more common development tool and as such, are of interest to Mylar. The first step for integrating this type of technology is to  
+
   becoming a more common development tool and as such, are of interest to Mylar. The first step for integrating this type of  
  extend Mylar's editing framework to support wiki style editing. Then prototype views, Eclipse forms, or embedded WYSIWYG editors will
+
  technology is to extend Mylar's editing framework to support wiki style editing. Then prototype views, Eclipse forms, or embedded  
  be explored as a means of providing this functionality to the user. The purpose of this phase is to help define the future of rich editing  
+
  WYSIWYG editors will be explored as a means of providing this functionality to the user. The purpose of this phase is to help  
  in Mylar through experimental interfaces.
+
  define the future of rich editing in Mylar through experimental interfaces.

Revision as of 17:48, 27 May 2006

Phase A: Bridging the Gap

 Mylar's expanding user base in the eclipse community is quickly making it a standard choice for eclipse integrated bug tracking. 
 It is not the only choice however, eclipse-bugzilla (a former project of mine) provides similar functionality for bug tracking. 
 There has been ongoing discussions on merging the two projects, but no action has been taken yet. Thus, the first phase of this 
 project will focus on bringing functionality from eclipse-bugzilla to Mylar. This list includes:
 - Support for bugzilla collections as query options
    * Collections are a new feature of bugzilla which allows products to be grouped
      into collections. Queries can also be made against a collection instead of 
      selecting the individual products.
 - Support for collection to product associations
    * When a collection is selected, the product list should update to reflect only
      the products in that colletion.
 - Support for the product to {component/version/milestone} associations
    * When a product is selected, the component/version/milestone lists should update
      to reflect only those which are associated with that product.
 Optionally:
 - A more user friendly query UI
    * Hide less commonly used options
    * Automatically synchronize query options with the repository
 - Automatic version detection of repositories
 - Support for applying attached patches directly to the workspace


Phase B: Full Feature Editing

 Mylar's bug editor provides a structured approach to composing comments for bug reports. In its current form it lacks full support 
 for bugzilla features. This phase of the project will focus on adding editor support for missing bugzilla features with high 
 quality integration into the platform. These features include:
 - Adding attachments
 - CC list management/selection
 - Voting (and viewing current tallies)
 Platform integration features include:
 - Drag-and-drop for attachments
 - Spellchecking
 Optional ideas:
 - Quoting comments


Phase C: Researching and Prototyping Future Editing Features

 Task repositories are beginning to support a richer editing via a wiki style syntax (eg. JIRA). In addition, wikis in general are 
 becoming a more common development tool and as such, are of interest to Mylar. The first step for integrating this type of 
 technology is to extend Mylar's editing framework to support wiki style editing. Then prototype views, Eclipse forms, or embedded 
 WYSIWYG editors will be explored as a means of providing this functionality to the user. The purpose of this phase is to help 
 define the future of rich editing in Mylar through experimental interfaces.