Related Topics: MaintainerIssues
, NTP-BUG 2548
, NTP-BUG 2512
, NTP-BUG 2216
, NTP-BUG 2053
, NTP-BUG 1687
, NTP-BUG 1365
, NTP-BUG 1106
, NTP-BUG 1055
Harlan's original Bugzilla wishlist
- I would like to see something like what issuezilla has, similar to "what" and "how important". With this in mind, I'd like to see the "what" category include:
- version (this filed could probably use an associated "date")
- unresolved means it's a target milestone
- resolved means it's a released milestone
- Issues scheduled for a particular release would automatically appear in the dependency chain for that release.
I now look at "Severity" as "how important is this to the reporter?" and "Priority" is "how important is it to the Project?". I notice pros and cons to Priority being generally visible, and it almost certainly should not be editable by users. There may be cases where an issue is not in the least "severe" but for some reason (like contractual obligation or to get a sale) it has a high priority. I suspect I'd like to see better documentation of some of these seemingly bizarre cases.
- As a release engineer for a particular milestone I want all "issues" that are slated for that milestone to also appear as "my bugs", in addition to being on the "my bugs" list for the assigned person.
With these features it should be pretty easy to come up with a mostly automated page that looks like subversion's project_status.html page. OK, it looks like that page is no longer available.
- The Release Engineer should be the only one to mark a bug as CLOSED
- The Release Engineer should be the only one to mark a bug as FIXED
Different products may have different needs in this area.
- At the moment, in Bugzilla, "enhancement" is conflated with the Severity field. But we could certainly add a custom field with values "Bug/Enhancement/Task".
Bugzilla has a Version field, and some people put dates in it. The other option is a custom date field to go alongside the version field, but that could lead to issues with the two getting out of sync unless one was careful. Another option would be to add custom UI to associate dates with versions, and it just displayed the current date for that version. Then, if the admin updated the date (e.g. if a release slipped), all bugs with that version would display the new date. This would require custom development.
We can change "who is allowed to edit what field" to your heart's content - just define what you want. There's a special hook for it.
With regard to "my bugs", you can do a Saved Search which finds what you want, and add it to the footer so the link is visible on all pages.
If you need a particular custom reporting page I can code that up for you pretty quickly. -- GervaseMarkham
- 17 Nov 2014
for information about how we've been using Bugzilla to help us with workflow.
For "code release" products, the Release Engineer needs to know when a developer has finished with a patch, so their development repo can be pulled in to the release repo. We do that via the RESOLVED/READY state.
I'd like to start getting code reviews built in to this process as well, but right now we don't have enough developers to do code reviews.
I run a custom report to show me READY bugs, and I take those, do some build testing on them, then integrate them into the distribution. I mark the bug as RESOLVED/FIXED, with a note to the reporter to please check the upcoming release and mark the bug as VERIFIED or IN_PROGRESS, as appropriate. We don't have a QA team to handle those checks.
There is no need for this workflow in non-code products.
Steve implemented a Security category recently - I can see some of the pros/cons of this approach, and I don't have a full grasp of the ramifications.
Anyway, from my POV when a developer marks a bug as READY the owner should change to me, because the developer may not care about anything else unless the bug is "reopened".
- It seems like your workflow conversations are full of history and specific requirements; I recommend a phone call to discuss all the options here, so I can blend your needs with best practice from elsewhere to make a recommendation. -- GervaseMarkham - 19 Nov 2014
We need to be careful about plaintext email updates to security-flagged bugs.
We need to be careful and aware of what happens when a security bug is opened, where email is sent, what our IRC
bot reports, what people who explicitly go to that bug number can see, etc.
In the old days we did not have a "security issues" component in the NTP Product. If we had a group restriction that controlled the information flow.
The choice for restricting security bugs via group restriction or using a separate component affects whether or not the default owner of the component will know about the issue (by default).
- There is a SecureMail extension to Bugzilla which allows you to mark a group as "requiring secure mail". Then, all email for bugs in that group are either sent encrypted (S/MIME or GPG supported) or you just get an email which says "Bug X changed" and nothing else. Mozilla uses this for our security bugs.
Keeping the data from the bot would be as simple as making sure that either:
* the account to which the bot subscribes is not a member of the security group; or
* the account to which the bot subscribes does not have an encryption key configured; or
* the bot doesn't know how to decrypt mail or doesn't have access to the decryption key.
People who explicitly visit a bug number they can't see get a "You are not allowed to see bug XXXX" message.
I'm very happy to expand more on how Mozilla handles security bugs in Bugzilla, but it works very well for us. -- GervaseMarkham
- 17 Nov 2014
Harlan understands there's a plugin that will allow folks to edit the description and comment fields (perhaps letting folks see the edit history).
Having this capability would be swell...
- Upstream, this is https://bugzilla.mozilla.org/show_bug.cgi?id=540 - a 3-digit bug which was resolved in 2018. However, I do share some people's caution about this feature. It's rather easy to abuse - people can morph bugs in ways which makes them hard to understand. You may want to restrict it to known-sane people -- original comment by GervaseMarkham - 17 Nov 2014, updated by DruLavigne 30 Sep 2022