Linaro Bugzilla

Linaro has now migrated all of its bug tracking needs to, which is powered by Bugzilla. This wiki page is meant as a guide and should answer most your questions. If you encounter issues, please contact your project manager or tech lead or ask on #linaro-pmo IRC room.

Reporting Bugs

  1. Log in to with your Linaro login account or, if you don't have one, create an account with the New Account link on the front page.

  2. Enter the bug using the template bugzilla provides you. The better your bug report, the higher the chance that your bug will be addressed quickly!.

  3. Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle.

Bug Details

The core of Bugzilla is the screen which displays a particular bug. It's a good place to explain some Bugzilla concepts. This bug is a good example. Note that the labels for most fields are hyperlinks; clicking them will take you to context-sensitive help on that particular field. Any field with a * is mandatory.

  1. Product:

    • In the engineering organization Product refers to the products in development that a group is working on. For example, the LEG Kernel product is released by the LEG segment group.
    • For Landing Teams Product refers to anything in development for the restricted teams. These teams are private by default.
  2. Component: If a product contains more that one component it will be listed here. Most Products contain only one component which is called ‘general’.

  3. Version: The version field defines the version (or JIRA Fix Version) of the software the bug was found in (not targeted at)

  4. Severity: This indicates how severe the problem is - from blocker ("application unusable") to trivial ("minor cosmetic issue"). When editing a bug, this field is titled "importance"

  5. Hardware: The platform that the bug was discovered on. If the specific hardware is not listed, use ‘other’ and describe the platform in the comments.

  6. OS: The operating system that the bug was discovered in.

  7. Summary: A one-sentence summary of the problem. This is the heading that will be shown when bug lists are displayed. A good summary explains the problem in clear and specific terms, but is often concise enough to fit within the default summary space in Bugzilla. You should be able to tell exactly what a bug is about just by reading the summary.

  8. Description: An overview and a more detailed restatement of summary. This should include

    • Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the bug. Include any special setup steps.
    • Actual Results: What happened after performing the above steps.
    • Expected Results: What should have happened, were the bug not present.
    • Additional Information:
  9. Attachment: If any attachments are relevant to the bug they can be added here.

Advanced Fields

Those fields will be visible when you click on the "Show Advanced fields". Most of the time, you don't need to alter them.

  • Assignee: The person responsible for fixing the bug identified by their email address. Every team has a default owner so if you are not sure, leave it.

  • CC: Any other people who should be receiving updated information on this bug. For private products, anyone on the CC: list will be able to view the bug information.

  • Alias: A short, unique name assigned to a bug in order to assist with looking it up and referring to it in other places in Linaro Bug Tracking System.

  • URL: Bugs can have a URL (if any exists) associated with them - for example, a pointer to a web site where the problem is seen.

  • Depends On: If this bug cannot be fixed unless other bugs are fixed the numbers are recorded here.

  • Blocks: If this bug stops other bugs being fixed the bug numbers are recorded here

Private Bugs supports restricted teams bugs by way of private bugs. Currently, private bugs are bugs that are assigned to private teams (products using Bugzilla terminology), which includes all the Landing Teams. Private bugs will be marked with "Private" in red.

Private bugs can only be accessed by the reporter, assignee, team the bug belongs to, and CC list. Unfortunately, bugzilla lacks the ability to mark a bug private or public. However, future plans include providing such functionality.

Life Cycle of a Bug

Lifecycle of a Bug

Searching for Bugs

Bugzilla has detailed documentation on how to search for bug, which you can find here.

Migrating bugs from Launchpad or JIRA to Bugzilla

Unfortunately there is no easy way to export Launchpad bugs to Bugzilla with history and attachments intact. It is recommended that bugs be closed on Launchpad as soon as possible. Any bugs that need to persist MUST be manually copied over to Linaro Bugzilla with any relevant history and attachment.

The following tables provide a mapping of the bugs in Launchpad and JIRA to in an effort to standardize the mapping between all three bug trackers.

Bug States

Launchpad or JIRA State

Bugzilla State

New, Incomplete, Opinon


Confirmed, Triaaaged


In Progress

In Progress


Resolved (resolution: Invalid)

Won't Fix

Resolved (resolution: Won't fix)

Fix Committed

Resolved (resolution: Fixed)

Fix Released


Duplicate bug

Resolved (resolution: Duplicate)

Bug Importance

Launchpad or JIRA Importance

Bugzilla Importance












Trivial, enhancement


Process/Bugs (last modified 2014-08-12 17:19:31)