| Summary: | Option to make a reverse engineering in query URLs | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Willian Mitsuda <wmitsuda> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | steffen.pingel |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Willian Mitsuda
It might be a good idea, however the major point of the "query from URL" is to be able to use query that you can't actually create using query configuration dialog. So, after editing such query you'll lose all parameters not supported byt that dialog. (In reply to comment #1) > It might be a good idea, however the major point of the "query from URL" is to > be able to use query that you can't actually create using query configuration > dialog. So, after editing such query you'll lose all parameters not supported > byt that dialog. > Agree, we should let the user choose if he wants or not Mylyn to try reverse engineering on URL. Actually that is not what I meant. If your contain any unsupported parameters, it should not allow to edit it in the dialog. How about a UI that allows to populate the search form from a URL. This could be a simple as adding a button to the query form. 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 |