openSUSE:Submitting feature requests

Jump to: navigation, search

In general: The openSUSE project includes a growing volunteer network of Linux users and developers who participate in the ongoing creation and improvement of openSUSE by testing development releases. This team of testers has a common mission: they improve the world's most usable Linux distribution by finding and constructively reporting relevant bugs.}}

We report bugs, submit enhancements reports, or provide patches in Bugzilla, the openSUSE bug tracking system. We want to use it for feature requests, too. By searching the system and providing clear, accurate details, we give developers an easy way to reproduce the defect and find quick solutions.

You're also welcome to implement your feature request directly as explained like with bugs in the fixing bugs documentation.

Accessing Bugzilla

To report a feature request on Bugzilla visit a page from the list below corresponding to the latest openSUSE version.
First you will see the login page. Bugzilla and openSUSE wiki logins are the same.

The rolling release version of openSUSE, Tumbleweed:

The following are officially maintained versions, maintained by openSUSE Maintenance Team that consists of SUSE security team and volunteers from community.

openSUSE Leap 15.1 is in development. You can test it and report bugs for volunteers in the community.

Next links can be used for openSUSE infrastructure, Build Service and all wiki servers:

You may use helper javascripts in your Opera or Firefox (with Greasemonkey extension) to make your work with openSUSE Bugzilla more comfortable.

Reporting a feature request

Some software components have special instructions for bug reporting/ feature requests, which you can find here:

Accessing Github

We have different upstream projects like OSEM and OBS. You can find those frojects on Github. Every project has a section with Issues. You can create feature requests there. At first you have to login with your github account. Add [Feature] in front of the title of your Issue.

Selecting the correct component and version number when reporting a feature request

Choosing the wrong product or component causes inefficient handling of your report, because it is initially assigned to the wrong people. Or it makes us wonder whether an already-fixed bug could possibly reappear in certain cases, which also creates unnecessary work. Choosing the correct product, component, and version is vital for us to quickly reproduce (and finally solve) your problem. So please be careful here.

  • The product '' is for bugs in this Wiki system on and bugs in itself only.

Voting in Bugzilla

Voting in Bugzilla is intended for orientation purposes only--not for specific prioritization or resource allocation.

  • For further information about voting, refer to voting page.