Improve plugin association in defect reporting

[Ryan J Ollos]

On tickets that are populated by clicking create on an error page, the Component is not set and so we rely on the user to set the Component field. Frequently they do not. I briefly investigated ways to solve this. We could add Component to the GET request:

trac/templates/error.html

@@ -58 +58 @@
     <input py:if="url == trac.homepage.strip('/')" type="hidden" name="version"
            value="${trac.version.split('-', 1)[0] if 'dev' in trac.version else trac.version}" />
     <input type="hidden" name="summary" value="$message" />
+    <input py:if="'trac' not in faulty_plugins[0]['info']" type="hidden" name="component" value="${faulty_plugins[0]['name']}" />
     <textarea name="description" rows="3" cols="10">
 ${description_en if url else description}</textarea>
     <span class="inlinebuttons">

That would only work in cases that the plugin name matches the project name. Frequently they do not, for example: SumStatsPlugin and TracSumStats​. Perhaps we could use IRequestHandler to handle some common mappings, such as TracSumStats -> SumStatsPlugin.

[Ryan J Ollos]

A better idea I think is to use url from setup.py via info.get('home_page') to extract the Component and pass it as a parameter in the GET request: ​t:browser:/branches/1.0-stable/trac/web/main.py?rev=12315&marks=561,586-587#L553.

[Ryan J Ollos]

See proposed change in ​trac:#11434.

[Ryan J Ollos]

Assuming upstream change will be accepted, closing this ticket for now.

[Ryan J Ollos]

Fixed in ​trac:#11434 for ​milestone:0.12.6 / ​milestone:1.0.2 / ​milestone:1.1.2.