How to Report Bugs

Visit our Bug Tracker page to learn more about Tizen Bug Tracker, which is based on JIRA.

Reporting an Issue

1. Getting Started

Go to and log into JIRA with your Tizen account. If you do not have a Tizen username, please go to and register for an account before using JIRA.

All of our community infrastructure, including the bug tracker, is subject to our community guidelines. Please review the community guidelines and the bug tracker guidelines before contributing to make sure that you understand the expectations and consequences of violating our guidelines.

2. Search First

Always search JIRA first, to see if your issue has already been reported. (JIRA provides a powerful issue search facility. You can search for issues across projects, versions, and components, using a range of search criteria. For more details, refer to the JIRA Document: Searching for Issues.

3. Create an Issue 

  • Click Create Issue at the top right of the screen to choose Project and Issue Type

    • Project. A JIRA project is a collection of issues, and, in most cases, it represents a software development project in Tizen.
    • Issue Type. Issue type is used to track different types of issues. For example, an issue could represent a software bug or a project task.

4. Add as Many Details as Possible

Fill in detailed information of your issue in Enter the details of the issue screen.

After your select Project and proper Issue Type, click Create, now you will go to Enter the details of the issue screen for filling in detailed information of your issue. Fields with a red asterisk (*) are required field and cannot be left as blank.

  • Component/s. High levels break down of project, based on functional modules.
  • Package. Lists Tizen packages, as well as their maintainers. The purpose of this field is to enable accurate disposition of issues to package level. When a package is selected, the package maintainer info will be popped up at the second level select box. This field is optional for reporter.
  • Affects Version/s. The version(s) of the software that the issue is detected or applies for.
  • Severity. The impact of the issue. Options include:
    • Critical. Intention: SW is not usable for intended purpose. SW with critical defects is not to be released.
    • Major. Intention: SW is not reliably usable for its intended purpose or use is significantly impaired. SW with major defects should not be released. If released, communication about the defect, such as a documented workaround, errata, or other communication, must be sent.
    • Normal. Intention: SW is usable and may be released, but only if the user is supplied with a workaround, errata, or other communication regarding the defect.
    • Minor. Intention: SW may be released without a communication regarding the defect and satisfies the following conditions: a) No impact to user's overall perception of SW quality. b) Tolerable impact to user experience with minimal support costs. c) Does not meet any of the criteria for other defect levels.
  • Profile/s. The types of device the issue has been identified in. Multiple selections are enabled if the issue applies for more than one type of device.
  • Platform/s. The hardware platform against which the bug is detected.
  • Summary. A brief summary of the issue.
  • Environment. The environment in which the issue is reproduced, including HW environment and SW environment, such as the device name and configuration, the build name, package version, etc.
  • Description. The detailed description of the issue. For bugs, the description section must include a
    detailed steps to reproduce, as well as the bug's impact to users.
  • Reproducibility. The reproducibility of the issue.
  • Attachment. Attachment which would help people understand or resolve the issue.
  • Labels. Labeling allows you to categorize an issue(s) in a more informal way than assigning it to a version or component. People could create a new label by editing in the label field, or reuse labels created by others by selecting from the drop-down list.
  • Source. The source of the issue.
  • External URL. Dependencies for bugs/requirements that reside on tools outside of JIRA.

Fill in the fields displayed in your issue reporting page with proper information, and click Create button at the bottom of the Enter the details of the issue screen. Congratulations, you are done reporting your bug!

Tizen Bug Workflow Diagram