Description of problem: [Usability]It is better show error message when click the commit button but without any version, component, release, milestone selected in the process_bug.cgi Version-Release number of selected component (if applicable): 4.4.6026 How reproducible: Always Steps to Reproduce: 1.Open a bug, select other product, then click button "save changes" quickly 2.In the process_bug.cgi, some fields are not selected, such as 'version','component'... 3.Click the button 'commit' Actual results: The page refreshed without any chagne except lost the group change info. Expected results: The page should show error message about which field isn't selected and need user select. Additional info:
(In reply to qgong from comment #0) > 1.Open a bug, select other product, then click button "save changes" quickly Do you mean that you clicked Save Changes before the compnent list had been populated? If so, that presumably means that you selected Fedora or a RHEL version as the product.
(In reply to Jason McDonald from comment #1) > (In reply to qgong from comment #0) > > 1.Open a bug, select other product, then click button "save changes" quickly > > Do you mean that you clicked Save Changes before the compnent list had been > populated? If so, that presumably means that you selected Fedora or a RHEL > version as the product. Yes, If we do action like this will cause some fields are not selected, such as 'version','component' in the In the process_bug.cgi page. I just want to say The process_bug.cgi page should show error message about which field isn't selected when click the button "commit" with version or component not selected.
It would probably be better to prevent the user submitting the form when required fields are empty. We already do that in some cases, such as when the user chooses an external tracker but doesn't enter the tracker ID.
In preparation for entering maintenance mode we are closing bugs that are unlikely to be scheduled in maintenance sprints.