English
What is observed when the issue occurs?
What does the user expect that should happen if the software behaved correctly?
*Version*: You should set this to the version of Fedora that you observed the bug on.
*Version-Release number of selected component (if applicable):*
*Use your Fedora account*: You can use your https://accounts.fedoraproject.org/[Fedora account] to sign into Bugzilla.
This is preferred, since your Fedora account can also be used to log into all other Fedora services.
This redirects to a new bug report template on the bug tracker. The image below shows a new bug template:
The version of the package should be specified here. Once the package name is known, the version can be obtained by using the `rpm` command:
These enable other users to verify the bug, and they also inform the developers of what specific steps cause the issue. It makes it much easier for them to look at the source code and pick out the bits that may be faulty.
These are some more resources for those looking to report better bugs by providing more information:
There are a few terms that are commonly used in this document:
The purpose of this document is to give step by step instructions on filing bugs in Fedora.
The following fields need to be set:
The Fedora Packages Web Application provides a convenient shortcut to file new bugs.
The Fedora Packages Web Application lists the bug reports for Gnome software at https://bugz.fedoraproject.org/gnome-software.
The CC list contains all users that should be notified when any updates are made to the report.
Terminology
*Summary*: You should provide a useful short summary of the issue here.
*Submit a report even if unsure*: If you aren't sure of what to fill in, you should still submit the bug report.
Maintainers can follow up with questions to gather more information.
*Steps to Reproduce:*
Step 3: Test updates