Version: unspecified OS: Linux I am not saying INSTEAD, just add the old engine. The reason: In current engine all steps are mixed together, it is impossible to automatize task of reporting even a bit. With old engine common parts were put together _at start_ so it was possible to save presets and then start reporting (for every new report) from the middle, after all presets were loaded. This was not supported explicitly but thanks to logical steps (order) it was possible to come up with URLs that put user in the middle, like this: https://bugs.kde.org/wizard.cgi?step=application&kdeVersion=KDE%204.4.3&distribution=SuSE%20RPMs Now, I have to _each time_ say, that yes, I use opensuse, thank you, that I use KDE 4.3.4, thank you, and it means 4 clicks more per each report. Count to 1000 reports, and you have 4000 clicks, not mentioning trouble and time which it takes. ============================ Alternative: reorder the steps -- put the common factors first: * KDE version * distro * system and then ask about the product and all the rest. Reproducible: Always
No. I'm not maintaining two separate ways to report bugs.
Ok, option b) Keep the single engine, current one, but please reorder the steps so the common factors would be first ones (they change also rarely comparing to others). Reasoning is in the original report.
Closing as invalid, the way of reporting bugs has changed. And also the steps are now on only 2 pages, while the first forces you to use an application only, the other steps have a single page.