“Powerful” flags in Bugzilla

Although Bugzilla has already provides powerful search and report function, we still want to get some special information from the Bugzilla. To get this, the additional flags sound powerful than we expected.

Here are some examples to show these powerful flags:

Example #1:

We can search out all bugs that have been set to REOPEN status by search, but how to know which bug is reopened by code fixing failed?

We set a flag named “FailedinQA”. So when the bug was reopened by a failed code fixing, we marked this flag to “+”. So, we can easily tell these actually failed bugs.

Example #2:

There are bugs were found after one round test case execution. We want to know all these bugs that still working on previous build.

We set a flag named “Regressed”. When the bug is verified working on previous build, the flag was set to “+”. Set to “-“means this is a new feature bugs or it not working on previous build too. So, the “-“marked bugs are missed one. We should take more regression test on these areas.

Example #3:

There are some bugs need to log into release note. So, technic writer need a way to search out all bugs easily.

We set a flag named “ReleaseNotesReq”. We marked all these bugs to “-” for the technic writer. The writer set to “+” means it has been updated into release notes.

Example #4:

Sometimes, the created bug is not create for a real issue, but created for an opening discussion. So, BA, Dev., and QA can work together on it for enter comments as logs.