fertlogin.blogg.se - Bugzilla screenshots

#Bugzilla screenshots how to
#Bugzilla screenshots code
#Bugzilla screenshots download
#Bugzilla screenshots windows

Summary is clear and specific enough to distinguish the reported bug from other similar ones.

Check for duplicates has been proceeded?.

The right moment for CONFIRMED is when all relevant information has been gained. Please do not change to CONFIRMED only because you were able to reproduce reporter's observations. When should I change Status from UNCONFIRMED to CONFIRMED? But of course, if you are an experienced bug tester (relevant contribution in more than 100 bugs or similar qualification), you might find good reasons to ignore the Two Men Rule and to select initial Status CONFIRMED So the answer is generally no! Even if you are pretty sure that you found a real bug and added lots of relevant information, generally following the Two Men Rule results in better reports, what leads to faster bug fixing costing less developer resources. The CONFIRMED status means that the bug report is clear enough and has sufficient details for another person to replicate the bug on another system.

Bug related to WW8 import filter (WW8 denotes the Microsoft Word binary file format - specification found here)īug STATUS CONFIRMED Should I report new bugs with initial Status CONFIRMED?.

Set the Issue Type selector to ENHANCEMENT instead.

deprecated for Request For Enhancement.

The "regression" keyword should be added to the Keywords field instead.

Deprecated tag for AOO regression issues.

They are often obsolete nowadays because some Bugzilla fields are better suited for marking the kind of bug.Įxamples for pseudo tags that were used are: In order to make bug summaries as concise as possible experienced bug reporters used pseudo tags directly in the summary.

Meaning of bracketed pseudo keywords in the summary

#Bugzilla screenshots code

If the integration of a code branch into the mainline has introduced problems then adding the branch tag also makes very much sense. So if a problem occurs only on a development branch then please use the bracketed branch name in the bug summary to make things as clear as possible. When such branches are tested the bugs found are very valuable for everyone working on that branch but of little value for the general public. But code in branches is mostly not yet ready for general consumptions and needs to be extensively tested before it can be integrated. Development branches are usually very interesting because they contain important new features or major cleanups. Meaning of bracketed branch names in the summaryĭevelopment often happens in code branches.

#Bugzilla screenshots windows

"Writer prints green text underlines as blue on a Windows GDI printer". So instead of having a summary "Bug in Writer!!!" please be more specific and write e.g. The more specific a bug summary is the more useful it is for others such as when you report a new bug you will notice that bugzilla tries to find similar bugs that might be of interest. It's recommended to add some meaningful texts at relevant places ("Here Indent is Wrong").īe as concise as possible in the bug Summary. For many cases there is a simple alternative: replace all characters by an "i": Often it is very hard or even impossible to remove all confidential text contents from a (Writer) document.

#Bugzilla screenshots how to

Replace all characters by "i" How to attach sample documents with confidential contents That saves time, because other users, who might know the existing attachment, do not need to check whether the new attachment contains new information (and only looks similar) or simply is a clone. If an appropriate document to reproduce the problem or to show the problem (screenshot) already does exist in Bugzilla, please cite the document instead of attaching it again. How to use attached sample documents for multiple Bug Reports Removing as much content that does not impact the reproducibility of the bug helps everyone who wants to work on that bug report. if you notice a bug in the upper left corner on page 345 of a 1000 page document then it is advisable to check whether the bug can still be replicated if the other pages are removed. Providing a sample document usually helps to reproduce a problem and to test the fix.

4.7 What is the best file type for screenshots?Īttachments and Sample Documents What are good Sample Documents?.

4.6 How to attach screenshots with additional graphic contents.

4.5 How to connect a Bug report to a Tracking Bug.

4.4 What is the appropriate Version in Bugzilla Version selector?.

#Bugzilla screenshots download

4.1 From where can I download latest test versions?.3.1.2 When should I change Status from UNCONFIRMED to CONFIRMED?.3.1.1 Should I report new bugs with initial Status CONFIRMED?.2.2 Meaning of bracketed pseudo keywords in the summary.2.1 Meaning of bracketed branch names in the summary.1.3 How to attach sample documents with confidential contents.1.2 How to use attached sample documents for multiple Bug Reports.