[Fedora QA] #356: Blocker Proposal is Slow

[Fedora QA]

#356: Blocker Proposal is Slow
--------------------------------------+------------------------
 Reporter:  tflink                    |       Owner:  tflink
     Type:  enhancement               |      Status:  new
 Priority:  major                     |   Milestone:  Fedora 19
Component:  Blocker bug tracker page  |     Version:
 Keywords:                            |  Blocked By:
 Blocking:                            |
--------------------------------------+------------------------
 = problem =

 While the blocker proposal functionality does work, the process of
 actually proposing the blocker is very slow - it appears as if the page
 has just stalled for a while as the request is being submitted to bugzilla

 Outside of being an annoyance, there is a possibility of users refreshing
 the page during submission, which would trigger a second proposal. This
 isn't the biggest issue ever but could end up generating extra comments in
 bugs.

 = analysis =

 It would be better to show users a "bug is proposing" page until the
 proposal is complete - that way they wouldn't be tempted to refresh the
 page and if the page is done correctly, it wouldn't matter if the page was
 refreshed or not.

 = enhancement recommendation =

 I have some ideas on how to go about fixing this but I need to explore the
 details before figuring out if any of them are even practical or how long
 the implementation would actually take.

-- 
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/356>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance