Closed
Bug 680094
Opened 14 years ago
Closed 13 years ago
requirements for bmo side of tell-us-more
Categories
(Input Graveyard :: Submission, enhancement, P1)
Input Graveyard
Submission
Tracking
(Not tracked)
RESOLVED
FIXED
4.4
People
(Reporter: glob, Assigned: davedash)
References
()
Details
Attachments
(1 file)
|
577 bytes,
text/plain
|
Details |
The following information is required from the Input team prior to the Tell-Us-More go-live.
Simple placeholder data will be used during development.
emails
* for all emails we need it in html and plain text, as well as the subject and sender
1. "follow this link to create a bmo account"
2. "follow this link to verify your existing bmo account
html pages
* can be styled to look like Input, but will be hosted on BMO
1. "bug created, and you now have a bmo account"
* It's a good idea to include a link to the "forgot password" as a
mechanism for the user to set their password
2. "bug created with your existing bmo account"
3. "something went wrong, here's the error"
Comment 1•14 years ago
|
||
For more information in regards to requirements, please take a look at the overview and mock-ups located in the PRD wiki:
https://wiki.mozilla.org/Firefox/TellUsMore
...For technical details for the BMO extension:
https://wiki.mozilla.org/BMO/TellUsMore
Assignee: nobody → tofumatt
Comment 2•14 years ago
|
||
Here's the e-mail content needed for e-mail verification. Please review if you'd like glob and tofumatt.
(In reply to Aakash Desai [:aakashd] from comment #2)
> Created attachment 562457 [details]
> e-mail content
>
> Here's the e-mail content needed for e-mail verification. Please review if
> you'd like glob and tofumatt.
that looks ok to me.
so you want the same email to cover both instances (new bmo account, existing bmo account), and you want to send a plain-text email only (no html) ?
Comment 4•14 years ago
|
||
Plain-text for now until we can get a little more professional and offer dazzling unicorns and gif'd Foxkeh animations.
Updated•14 years ago
|
Priority: -- → P1
Target Milestone: --- → 4.x
Updated•14 years ago
|
Target Milestone: 4.x → 4.5
Updated•14 years ago
|
Target Milestone: 4.5 → 4.4
| Assignee | ||
Updated•14 years ago
|
Assignee: tofumatt → dd
| Assignee | ||
Comment 6•14 years ago
|
||
aakash/glob,
This bug is confusing. What needs to happen on the Input side?
As I understand it:
* A form needs to be created.
* It's contents are sent via API to BMO [?]
* An email is sent from Input to the user letting them know they need to verify their email [?]
The requirements seem to say something different.
Also I don't know what the HTML/plaintext email thing is all about?
the basic flow of tell-us-more is:
1. a form (hosted on input) gathers the required data from the user
2. it posts to bmo using the new webservice methods from bug 678146 (xml-rpc)
3. bmo creates the bug, sends the emails, returns an id to input (not the bug-id, just a row-id)
4. some sort of thanks-you page is displayed (also hosted in input)
5. when the user clicks on the url in the email, bmo makes the bug real, and displays a thank-you page
this bug is just about the content that the bmo extension needs to be completed; it doesn't cover any of the input-specific work (steps 1, 2, and 4). i suspect there's another bug tracking that.
all i need in order for this bug to be resolved are the 3 html pages requested in comment 0. i'm expecting these to be static pages, with placeholders for displaying the reporter's email, bug id, etc. these pages will be displayed after the user verifies their email address (ie. step 5). it would make sense if the pages were styled to look like input, rather than bmo.
aakash has already provided the content for the emails, no need to do any wordsmithing there :)
Comment 8•14 years ago
|
||
What glob said.
| Assignee | ||
Comment 9•14 years ago
|
||
glob,
How's this for the first HTML page?
bug+account:
http://cl.ly/0p2C162Y3o382O2z192L
bug:
http://cl.ly/0N1p1O0C0B2i18181p3o
error:
http://cl.ly/3U3r3R0v3j1f3p3y1S2W
How will l10n work with all this?
| Reporter | ||
Comment 10•14 years ago
|
||
(In reply to Dave Dash [:davedash] from comment #9)
> glob,
>
> How's this for the first HTML page?
for the new account page it may be a good idea to include instructions on how to set the password for the account. when we have to create an account, we create it without a password (so they can't login). they need to perform a password reset to gain access to their account.
i would expect something like (from a content, not wording, point of view):
--
<a>Bug number 12345678</a> has been filed, and we have created a Bugzilla account for you.
Before you can use your Bugzilla account you are required to <a>set your password</a>.
--
> How will l10n work with all this?
bugzilla is english only, with respect to the UI and the bugs filed (with a few exceptions).
i don't think non-english bugs should be created from input via this tool (for now).
| Reporter | ||
Comment 11•13 years ago
|
||
as detailed in bug 719711 we're going to do a redirect for the confirmation/error pages.
so the only thing i need before i can resolve this bug is a subject and sender for the email.
for now i'll go with:
Subject: Thank you filing a bug on Firefox!
From: Do Not Reply <nobody@mozilla.org>
for both emails (new-account and existing-account).
Comment 12•13 years ago
|
||
Hrm, its a bit too impersonal to say "Do Not Reply" as the from. Can it be addressed from the "Mozilla Development Team" or something along those lines?
| Reporter | ||
Comment 13•13 years ago
|
||
(In reply to Aakash Desai [:aakashd] from comment #12)
> Hrm, its a bit too impersonal to say "Do Not Reply" as the from. Can it be
> addressed from the "Mozilla Development Team" or something along those lines?
done.
i've pushed the changes to bugzilla-stage-dev, marking this bug as fixed :)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Input → Input Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•