Fix proposal form processing to actually use submitted data. Fixes T848
ClosedPublic

Authored by tflink on Sep 28 2016, 11:21 PM.

Details

Summary

Changes the way that the bug proposal form is displayed in HTML and processed in Flask so that we're not dropping the submitted data needed to process the blocker request

Test Plan

Load the proposal page, note that the bugzilla username is filled out and the default milestone is properly set. Submit a test blocker/FE (doesn't need to actually go to BZ), make sure that no data was dropped from the form

Diff Detail

Repository
rBLKR blockerbugs
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
tflink retitled this revision from to Fix proposal form processing to actually use submitted data. Fixes T848.Sep 28 2016, 11:21 PM
tflink updated this object.
tflink edited the test plan for this revision. (Show Details)
tflink added a reviewer: mkrizek.
mkrizek accepted this revision.Sep 29 2016, 10:25 AM

Thanks for the fix. I could have sworn it worked for me when I tested the patch. :/

I wonder what broke disabled=True. Hasn't it been working for a while now?

This revision is now accepted and ready to land.Sep 29 2016, 10:25 AM

Thanks for the fix. I could have sworn it worked for me when I tested the patch. :/

I wonder what broke disabled=True. Hasn't it been working for a while now?

It was the bugform.process() that changed things. We weren't setting the default before, so that call wasn't needed and without that call, it didn't care that the bz_user field didn't exist in the request.form of the POST request.

This revision was automatically updated to reflect the committed changes.