Community
Participate
Working Groups
BugEditor suggests wrong version number Im using eclipse 3.3.0 but the editor suggests version 3.4
Created attachment 75947 [details] Screenshot
I like this suggestion. Mylyn's Task Editor does not currently have any special rules for the bugs.eclipse.org repository. To implement this we would need to add the following rule: * If the repository is bugs.eclipse.org * And the selected product is one of the SDK products (e.g. JDT, Platform) * Then set the Version attribute to the Eclipse version Since this rule could be used for any bugs.eclipse.org product (e.g. Mylyn) it would be best to make this rely on a plug-in to Bugzilla Product/Component mapping (bug 150278) rather than hard-coding the rule. The right home for this would be the org.eclipse.mylyn.bugzilla.ide plug-in, which is currently responsible for adding the bugs.eclipse.org repository. Tagging this for bugday since it could be a fun one for someone to try when the next bugday comes around.
One observation that should be taken into account: the reported bug may not necessary affect the same plugins installed in the environment that Task Editor is running on.
I've wondered the same thing about the Platform and OS attributes too. Quite regularly I file bugs that are not specific to my OS and manually changes this. So I wonder if we should have an option, on by default, along the lines of "auto-fill attributes" for new bugs.
To me this should be a repository or even project-specific option. Unless we could record params of the previously reported issues and reused them for new submissions for the same project or component.
+1 on making it repository-specific, related to changes that Rob is suggesting on bug 159397.
The version field will now be set when reporting bugs from the error log. The matching uses repository mappings (bug 150278) given that a feature id is provided and the feature is installed.
