Bugzilla Understanding a Bug - Bugzilla Bug Tracking System

How to understanding a bug?

The principle include or the core of Bugzilla is the page that shows subtle elements of a bug. Note that the names for most fields are hyperlinks; clicking them will take to setting touchy help of that specific field. Fields stamped * may not be available on each establishment of Bugzilla.

  • Summary − It is a one-sentence outline of the issue, which is shown in the header alongside the bug number. It is like the title of the bug that gives the user a diagram of the bug.
  • Status (and Resolution) − These characterize status of the bug – It begins with even before being affirmed as a bug, at that point being settled and the fix being affirmed by Quality Assurance. The distinctive conceivable values for Status and Resolution on establishment ought to be archived in the setting touchy help for those things. Status underpins Unconfirmed, Confirmed, Fixed, In Process, Resolved, Rejected, and so forth.
  • Alias − An Alias is a remarkable short content name for the bug, which can be utilized rather than the bug number. It gives the remarkable identifiers and help to discover the bug in the event of Bug ID isn't convenient. It tends to be helpful while scanning for a bug.
  • Product and Component − Bugs are isolated results and Components. A Product may have at least one Components in it. It arranges the bugs and aides in isolating them also.
  • Version − The "Form" field more often than not contains the numbers or names of the discharged variants of the product. It is utilized to demonstrate the version(s) influenced by the bug report.
  • Hardware (Platform and OS) − These demonstrate the tried condition or the working framework, where the bug was found. It likewise gives out the subtle elements of the equipment like RAM, Hard Disk Size, Processor, and so forth.
  • Importance (Priority and Severity) − The Priority field is utilized to organize bugs. It tends to be refreshed by the chosen one, businessmen or another person from partners with the expert to change. It is a smart thought not to change this field on different bugs, which are not raised by a man. The default values are P1 to P5.
  • Severity field − The Severity field demonstrates how extreme the issue is—from blocker ("application unusable") to insignificant ("minor corrective issue"). User can likewise utilize this field to show whether a bug is an improvement or future demand. The basic strong seriousness statuses are – Blocker, Critical, Major, Normal, Minor, Trivial and improvement.
  • Target Milestone − It is a future date by which the bug is to be settled. Model – The Bugzilla Project's points of reference for future Bugzilla adaptations are 4.4, 5.0, 6.0, and so forth. Points of reference are not limited to numbers however the user can utilize any content strings, for example, dates.
  • Assigned To − A Bug is alloted to a man who is dependable to settle the bug or can check the believability of the bug dependent on the business necessity.
  • QA Contact − The individual in charge of value confirmation on this bug. It might be the correspondent of the bug to give more subtle elements whenever required or can be reached for retest the deformity once it is settled.
  • URL − A URL related with the bug, assuming any.
  • Whiteboard − A freestyle content region for including short notes, new perceptions or retesting remarks and labels to a bug.
  • Keywords − The manager can characterize watchwords that can be utilized to tag and classifications bugs — for e.g. crash or relapse.
  • Personal tags − Keywords are worldwide and noticeable by all users, while Personal Tags are close to home and must be seen and altered by their creator. Altering those labels won't send any notices to different users. These labels are utilized to monitor bugs that a user actually thinks about, utilizing their very own arrangement framework.
  • Dependencies (Depends On and Blocks) − If a bug can't be settled as some different bugs are opened (relies upon) or this bug stops different bugs for being settled (obstructs), their numbers are recorded here.

Dependency Tree Link

Clicking on the Dependency tree link demonstrates the reliance connections of the bug as a tree structure. A user can change how much profundity to show and conceal the settled bugs from this page. A user can likewise fall/extend conditions for each non-terminal bug on the tree see, utilizing the [-]/[+] catches that show up before the rundown.

  • Reported − It is the Time and Date when the bug is logged by a man in the framework.
  • Modified − It is the Date and Time when the bug was last changed in the framework.
  • CC List − A rundown of individuals who get mail when the bug changes, notwithstanding the Reporter, Assignee and QA Contact (whenever empowered).
  • Ignore Bug Mail − A user can check this field in the event that he never needs to get an email notice from this bug.
  • See Also − Bugs, in this Bugzilla, other Bugzilla or other bug trackers those are identified with this one.
  • Flags − A banner is a sort of status that can be determined to bugs or connections to show that the bugs/connections are in a specific state. Every establishment can characterize its very own arrangement of banners that can be determined to bugs or connections.
  • Time Tracking − This frame can be utilized for time following. To utilize this component, a user must be an individual from the gathering determined by the time tracking group parameter.
  • Orig. Est. − This field demonstrates the first evaluated time.
  • Current Est. − This field demonstrates the current evaluated time. This number is ascertained from Hours Worked and Hours Left.
  • Hours Worked − This field demonstrates the quantity of hours dealt with the specific imperfection.
  • Hours Left − This field demonstrates the Current Est. - Hours Worked. This esteem + Hours Worked will turn into the new Current Estimated.
  • %Complete − This field demonstrates how much level of the errand is finished.
  • Gain − This field demonstrates the quantity of hours the bug is in front of the Original Estimated.
  • Deadline − This field demonstrates the due date for this bug.
  • Attachments − A user can append documents (proof, test cases or fixes) to bugs. On the off chance that there are any connections, they are recorded in this area.
  • Additional Comments − A user can add remarks to the bug talk here, if user/analyzer has something advantageous to state.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Bugzilla Bug Tracking System Topics