Errors filing a bug do not open the bug report fields

[Matt Giuca]

1. Go to the bug report page on a project (/+filebug).
2. Type in a summary that is similar to an existing bug. LP displays the similar bugs.
3. Click "No, I need to report a new bug".
4. Fill in the bug details, but cause an error. For example, type an invalid username in "Assign to".
5. Click "Submit Bug Report".

The page you are redirected to says "Is "<your bug summary>" one of these bugs?" with the list of similar bugs. There is no indication that an error has occurred or how to proceed, or even how to get your bug's description text back.

Eventually, you may realise that if you click "No, I need to report a new bug" it opens up the rest of the page, which says "There is 1 error" and contains the text you had just typed in and points out where the error occurred. The problem is that the JavaScript was hiding it initially.

It should fully expand this out immediately if there is an error on the page.

[Robert Collins (lifeless)]

This is a dupe I think; I don't have the other number handy. Its
probably tagged under 'confusing-ui'.

[Matt Giuca (mgiuca)]

Hi Robert. I think I found it: bug #636188. That bug is about merge proposals, not bug reports, but it sounds like the same bug, so I've marked as a dupe and left a comment there.

[Curtis Hovey (sinzui)]

This is not a dupe of 892947. This bug require a code change to the bug reporting views where the setError method must be explicitly called with an explanation.

[Matt Giuca (mgiuca)]

Sorry :(