Description of problem: I've just got a crash in non-Fedora package. So the reporting failed at the first try, as I forgot to set the Product in Bugzilla settings. But even after going back and fixing that, it failed because the package name does not match any component available in that product. Now I don't have any option to go back and change the component, as there's no configuration option for that ... But I would like to suggest a bit different approach: Abrt knows what the problem is, now I got this error message: fatal: RPC failed at server. There is no component named 'qa-tools-workstation' in the 'QA Tools' product. so, if such situation appears, I'd suggest opening a dialogue which would allow to choose from available products, then trying again then if the product is set and the component does not match, open a dialogue allowing choosing from components of the selected product, then try again and so on for other needed fields (I guess at least Version may cause such problem too) maybe it could be just one dialogue - start with empty, after choosing product, reload the versions list, after choosing version, reload the components list ...
And how many dialogs should it open before it dies? I would like to hear opinion of some UX designer before we start implementing this.
(In reply to Jiri Moskovcak from comment #1) > And how many dialogs should it open before it dies? as many as needed to match Bugzilla options? being able to report bug after answering a few questions seems to me 100% better user experience than not being able to report the bug :-) > I would like to hear opinion of some UX designer before we start implementing > this. I believe you had some advisor when creating the new GUI, pls could you set NEEDINFO on that person here?
*** Bug 833052 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Dialog spam is definitely not the way to go, and in general this more sounds like a problem with your setup. No regular user will understand any of this. Which Bugzilla instance are you using? What package is it?