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 |
(→Platform integration features include:) |
||
| (36 intermediate revisions by 6 users not shown) | |||
| 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. 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 == | |
| − | + | === - ''[PENDING]'' 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. | |
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=148535 bug 148535] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | === - ''[PENDING]'' Support for collection to product associations === | |
| + | * When a collection is selected, the product list should update to reflect only the products in that colletion. | ||
| + | * Pending [https://bugs.eclipse.org/bugs/show_bug.cgi?id=148535 bug 148535] | ||
| − | |||
| + | === - ''[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 Mylyn team''' | ||
| − | '' | + | === - ''[COMPLETE]'' Persist query parameters === |
| − | + | * When the query dialog is opened, the widgets should be initialized to the previous query parameters | |
| − | + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=142891 bug 142891] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | == 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. | |
| + | === - ''[PENDING]'' Support for applying attached patches directly to the workspace === | ||
| + | * Apply patches attached to bugzilla reports directly to the workspace | ||
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=103932 bug 103932] | ||
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=98707 bug 98707] | ||
| − | '''Phase C:''' ''Researching and Prototyping Future Editing Features'' | + | |
| − | + | === - ''[PENDING]'' Parsing name -> email address associations === | |
| − | a more common development tool and as such, are of interest to | + | * Parse the proper names of people for display purposes. |
| − | + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=141390 bug 141390] | |
| − | 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 | + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=152415 bug 152415] |
| − | in | + | |
| + | === - ''[COMPLETE]'' Generating bug reports from the PDE Error log === | ||
| + | * Use errors from the PDE error log to generate a bugzilla report | ||
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=135605 bug 135605] | ||
| + | |||
| + | |||
| + | === - ''[COMPLETE]'' Auto-detect duplicate bug reports === | ||
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=143567 bug 143567] | ||
| + | |||
| + | |||
| + | === - ''[COMPLETE]'' Auto-attach context === | ||
| + | * Upload Mylar context whenever a patch is submitted | ||
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=148903 bug 148903] | ||
| + | |||
| + | |||
| + | = '''Phase B:''' ''Full Feature Editing'' = | ||
| + | Mylyn'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 == | ||
| + | === - ''[COMPLETE]'' Adding attachments === | ||
| + | * Add attachments to be uploaded with bug reports/comments | ||
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=102851 bug 102851] | ||
| + | |||
| + | |||
| + | === - ''[COMPLETE]'' Support attachment actions === | ||
| + | * Perform actions with attachments such as saving, copying to clipboard, applying a patch, etc... | ||
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=145787 bug 145787] | ||
| + | |||
| + | |||
| + | === - 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 | ||
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=102854 bug 102854] | ||
| + | |||
| + | |||
| + | == Platform integration features include: == | ||
| + | === - ''[COMPLETE]'' Drag-and-drop for attachments === | ||
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=149095 bug 149095] | ||
| + | |||
| + | |||
| + | === - ''[COMPLETE]'' Spellchecking === | ||
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=103093 bug 103093] | ||
| + | |||
| + | == 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 Mylyn. The first step for integrating this type of technology is to extend Mylyn'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 Mylyn through experimental interfaces. | ||
| + | |||
| + | [[Category:Mylyn]] | ||
| + | [[Category:SOC]] | ||
Latest revision as of 21:06, 29 October 2020
Contents
- 1 Phase A: Bridging the Gap
- 1.1 Phase A Tasks
- 1.2 Optional Ideas:
- 1.2.1 - A more user friendly query UI
- 1.2.2 - Automatic version detection of repositories
- 1.2.3 - [PENDING] Support for applying attached patches directly to the workspace
- 1.2.4 - [PENDING] Parsing name -> email address associations
- 1.2.5 - [COMPLETE] Generating bug reports from the PDE Error log
- 1.2.6 - [COMPLETE] Auto-detect duplicate bug reports
- 1.2.7 - [COMPLETE] Auto-attach context
- 2 Phase B: Full Feature Editing
- 3 Phase C: Researching and Prototyping Future Editing Features
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
- [PENDING] 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.
- bug 148535
- [PENDING] Support for collection to product associations
- When a collection is selected, the product list should update to reflect only the products in that colletion.
- Pending bug 148535
- [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 Mylyn team
- [COMPLETE] Persist query parameters
- When the query dialog is opened, the widgets should be initialized to the previous query parameters
- bug 142891
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.
- [PENDING] Support for applying attached patches directly to the workspace
- Apply patches attached to bugzilla reports directly to the workspace
- bug 103932
- bug 98707
- [PENDING] Parsing name -> email address associations
- Parse the proper names of people for display purposes.
- bug 141390
- bug 152415
- [COMPLETE] Generating bug reports from the PDE Error log
- Use errors from the PDE error log to generate a bugzilla report
- bug 135605
- [COMPLETE] Auto-detect duplicate bug reports
- [COMPLETE] Auto-attach context
- Upload Mylar context whenever a patch is submitted
- bug 148903
Phase B: Full Feature Editing
Mylyn'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
- [COMPLETE] Adding attachments
- Add attachments to be uploaded with bug reports/comments
- bug 102851
- [COMPLETE] Support attachment actions
- Perform actions with attachments such as saving, copying to clipboard, applying a patch, etc...
- bug 145787
- 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
- bug 102854
Platform integration features include:
- [COMPLETE] Drag-and-drop for attachments
- [COMPLETE] 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 Mylyn. The first step for integrating this type of technology is to extend Mylyn'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 Mylyn through experimental interfaces.