#350: Integrate Bugzilla Email Association with Blocker Proposal
--------------------------------------+------------------------
Reporter: tflink | Owner: tflink
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 19
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: 347 |
--------------------------------------+------------------------
= problem =
Once the functionality for bugzilla email verification and association
with FAS account is complete, it needs to be integrated into the proposal
process.
= analysis =
The process should look something like:
1. before showing the proposal page, check to see if there is an
associated bugzilla email
* If there is an associated email, go on to the proposal page
* If there is no associated email, redirect to another page that asks
for bugzilla credentials
2. After bugzilla email verification is successful, redirect to the
proposal page
= enhancement recommendation =
The process should be relatively simple, a new form and some more logic to
the proposal endpoint. Ideally, the redirect would be stored during the
process so that the user is sent back to their intended destination after
bugzilla email verification.
--
Ticket URL: <
https://fedorahosted.org/fedora-qa/ticket/350>
Fedora QA <
http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance