Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Mylyn/SOC/2006/Bugzilla Connector Enhancements"
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 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: | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | == Phase A Tasks == | |
| − | + | === - 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. | |
| − | + | ||
| − | + | ||
| − | |||
| − | + | === - ''[REMOVED]'' 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. '''This feature was already completed by the Mylar team''' | ||
| + | == Optional Ideas: == | ||
| + | === - A more user friendly query UI === | ||
| + | * Hide less commonly used options | ||
| + | * Automatically synchronize query options with the repository | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | === - Automatic version detection of repositories === | |
| − | + | * Detect the version of the repository rather than have the user input it. | |
| − | + | ||
| − | |||
| − | |||
| + | === - Support for applying attached patches directly to the workspace === | ||
| + | * Apply patches attached to bugzilla reports directly to the workspace | ||
| − | '''Phase C:''' ''Researching and Prototyping Future Editing Features'' | + | === - Parsing name -> email address associations === |
| − | Task repositories are beginning to support a richer editing via a wiki style syntax (eg. JIRA). In addition, wikis in general are | + | * Parse the proper names of people for display purposes. |
| − | + | ||
| − | + | ||
| − | + | === - Generating bug reports from the PDE Error log === | |
| − | + | * Use errors from the PDE error log to generate a bugzilla report | |
| + | |||
| + | |||
| + | = '''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: | ||
| + | |||
| + | == Phase B Tasks == | ||
| + | === - ''[IN PROGRESS]'' Adding attachments === | ||
| + | * Add attachments to be uploaded with bug reports/comments | ||
| + | |||
| + | |||
| + | === - CC list management/selection === | ||
| + | * Add user friendly CC list control for managing and selecting CC list members | ||
| + | |||
| + | |||
| + | === - Voting (and viewing current tallies) === | ||
| + | * Support voting and viewing current tallies of votes on bug reports | ||
| + | |||
| + | |||
| + | == 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. | ||
Revision as of 13:41, 31 May 2006
Contents
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:
Phase A Tasks
- 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.
- [REMOVED] 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. This feature was already completed by the Mylar team
Optional Ideas:
- A more user friendly query UI
- Hide less commonly used options
- Automatically synchronize query options with the repository
- Automatic version detection of repositories
- Detect the version of the repository rather than have the user input it.
- Support for applying attached patches directly to the workspace
- Apply patches attached to bugzilla reports directly to the workspace
- Parsing name -> email address associations
- Parse the proper names of people for display purposes.
- Generating bug reports from the PDE Error log
- Use errors from the PDE error log to generate a bugzilla report
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:
Phase B Tasks
- [IN PROGRESS] Adding attachments
- Add attachments to be uploaded with bug reports/comments
- CC list management/selection
- Add user friendly CC list control for managing and selecting CC list members
- Voting (and viewing current tallies)
- Support voting and viewing current tallies of votes on bug reports
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.