Community
Participate
Working Groups
When creating new tasks with the stack trace, Search for duplicates should run automatically in the background and show a popup dialog if it finds any.
By the way, we should be able to run this search for duplicated issues even when falling into web-based editor. So, stack trace copied to clipboard can be used to kick the search.
I'm not sure it is a good idea to always run it because there are cases where the user know that there are no duplicates, and the performance of the search is determined by the network speed. That's not to say that we shouldn't encourage it more. Btw, we currently rely on the search view for showing duplicates because it means that we didn't need to add a bunch of UI for the purpose of previewing reports in a dialog. However, the dialog could simply indicate that a duplicate was found, and ask the user what to do.
Mik, if search speed is related to the network speed that it is better to kick it as early as possible (maybe worth to have a preference to enable that). Then if there are some hits, popup can be shown to offer user to open the Search view with the results. PS: Ideally it would be nice to show the progress bars for such kind of tasks somewhere in the editor...
Need to defer: http://wiki.eclipse.org/index.php/Mylyn/3.0_Plan#Deferred_Items Tentatively scheduling for 3.1.
Created attachment 149325 [details] example of the web based launchpad bug reporting
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
