<head>
<title>$gProject $gBugs - how to report a $gBug</title>
<link rev="made" href="mailto:$gMaintainerEmail">
+ <link rel="stylesheet" href="$gWebHostBugDir/css/bugs.css" type="text/css">
</head>
<body>
<h2>Important things to note <strong>before</strong> sending</h2>
-<p>Please don't report several unrelated $gBugs - especially ones in
-different packages - in a single $gBug report.
+<p>Please don't report multiple unrelated $gBugs - especially ones in
+different packages - in a single $gBug report. It makes our lives much
+easier if you send separate reports.
<p>You should check if your $gBug report has already been filed by someone
else before submitting it. Lists of currently outstanding $gBugs are
Version: <something>
</pre>
-<p>Replace <code><something></code> with the version of the package.</p>
+<p>Replace <code><something></code> with the version of the package.
+Please don't include any text here other than the version itself, as the
+$gBug tracking system relies on this field to work out which releases are
+affected by the bug.</p>
<p>You need to supply a correct <code>Package</code> line in the
pseudo-header in order for the $gBug tracking system to deliver the message
<a href="Developer.html#tags">developers' documentation</a>.
Separate multiple tags with commas, spaces, or both.
+<pre>
+User: <<var>username</var>>
+Usertags: <<var>usertags</var>>
+</pre>
+
+<p>Replace <<var>usertags</var>> with one or more usertags.
+Separate multiple tags with commas, spaces, or both. If you specify a
+username, that users tags will be set. Otherwise, the email address of
+the sender will be used as the username</p>
+
<h2>Not forwarding to the mailing list - minor $gBug reports</h2>