Closed Bug 950974 Opened 11 years ago Closed 11 years ago

Common Response for Firefox OS (Basic Information)

Categories

(support.mozilla.org :: Forum, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: guigs, Unassigned)

Details

DESCRIPTION: 
NEEDED a common response for all of the build information and phone type when asking a Firefox os question in the Forum. 




DRAFT by Ralph and Rachel and Hermina

I understand that you are having problems with ***paraphrase the user's issue***. So that we may better understand and investigate the issue that you are encountering, please reply to this message with the following information: 
* What is the model of your phone? (ZTE Open, LG Fireweb, Alcatel OneTouch Fire) 
* What is the Build ID of your phone, found in the Device Information page? Please click on [http://mzl.la/Gzz6Kp this link] if you need help finding the Build ID of your phone. 
* Please provide the exact steps to replicate the issue you are encountering. << this item would also let us know which feature the user is having issues with. 
* What cell phone carrier are you currently using? 
* How often do you encounter this issue? 

Please be sure to include as much detail as possible, including any websites that may exhibit this issue, and any error messages that you may be receiving, exactly as they appear. This will ensure that we have all the information needed to investigate this problem. Thanks for your help, we look forward to hearing from you! 

We look forward to your reply.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
I was reviewing recently fixed bugs and saw this one. A bug didn't need to be filed on this so I'll mark it "Invalid".  

For the record: 
New response: https://support.mozilla.org/en-US/kb/forum-response-request-firefox-os-info
Discussion: https://support.mozilla.org/en-US/kb/forum-response-request-firefox-os-info/discuss

Andrew/feer56 added it to https://support.mozilla.org/en-US/kb/common-forum-responses on Dec 17th 2013, which is what made it appear in the list of available common responses.
Resolution: FIXED → INVALID
You need to log in before you can comment on or make changes to this bug.