Closed Bug 861432 Opened 13 years ago Closed 13 years ago

[AAQ Flow] Add Firefox OS and Marketplace

Categories

(support.mozilla.org :: Questions, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED
2013Q2

People

(Reporter: ibai, Assigned: rehandalal+mozilla)

References

Details

(Whiteboard: u=user c=aaq p=1 s=2013.10)

We need to add FxOS and Marketplace to the AAQ flow. Designs and decision tree to follow.
Blocks: 861430
No longer depends on: 861430
Bram's proposal is to start with 3 basic categories: 1- Something is wrong/fix problems 2- Customize controls and settings 3- Firefox Marketplace apps and payment We should match the articles that we promote on each of this steps to the following (same order): 1- Fix slowness, crashing, error messages and other problems 2- Customize controls, options, settings and preferences 3- Download and install apps Once we have the new FxOS taxonomy we can reevaluate this basic topics. After talking to Patrick, for now, we are not enabling the direct escalation to Zendesk through the AAQ flow. Meaning, if users have a problem with payments, they need to escalate to their carrier. We should create an article that covers that and it's promoted in the Firefox Marketplace path. Michelle, Patrick..does this work for you?
Flags: needinfo?(pmcclard)
Flags: needinfo?(mluna)
That works for me.
Flags: needinfo?(pmcclard)
I think that we are good to go with this as a first pass. We need the icon for the product. If we don't have anything better in time, let's use the regular Firefox icon and change it afterwards.
Flags: needinfo?(mluna)
Whiteboard: u=user c=aaq p= s=2013.10
I am pretty sure that the icons are the same for Firefox OS and Desktop Firefox.
Joshua..you are correct. we are looking to have an image (not necessarily the Firefox OS icon) that helps differentiate one from the other.
Hi, This works for me to have just three categories, I think I'd like them to match the wording of the final topics. I'd like to also play with a small form to request the user to tell us what device they are using in the question/system details. Thanks! Michelle
Matching the wording should be ok. Let's go with that to keep consistency with the rest of the products. I'm opening a different bug for the device.
I can't tell if this is this fully decided and defined? Are we adding two new products or just FxOS? What topics do we list for each? Are the topics in Comment 2 for both products? Are we sending users to the form that submits to zendesk?
Priority: -- → P2
Target Milestone: --- → 2013Q2
Ricky: We are just adding Firefox OS. Marketplace it's just a component of it. We will have this 3 categories as the Topics: 1- Fix slowness, crashing, error messages and other problems 2- Customize controls, options, settings and preferences 3- Download and install apps And all of them land into the forum. No Zendesk. For direct 1:1 support, end users need to call their carrier or contact the phone manufacturer.
Ah, I think I get it now thanks! Should be easy~ish. It is mostly (only?) question_config.py changes. Based on that I think this is 1pt.
Whiteboard: u=user c=aaq p= s=2013.10 → u=user c=aaq p=1 s=2013.10
Assignee: nobody → rdalal
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
The copy on this bug wasn't respected when landed into code: In the file apps/questions/question_config.py in line 141 we pushed: + 'name': _lazy(u'Customize controls, options and add-ons'), As per comment 10, it should be: + 'name': _lazy(u'Customize controls, options, settings and preferences'), Add-ons don't exist in Firefox OS. Thanks!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
:Ibai: I filed https://github.com/mozilla/kitsune/pull/1439 to fix the text issue. Does that look right?
Mike! That's perfect. Thanks for the quick fix!
I just pushed this to prod.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
For some reason, tapping the https://support.mozilla.org/en-US/questions/new link from the FF OS FAQ article when using a GP Keon points to a 404 / Page not found message, while it does work for desktop and Android. As Andrew pointed me to this bug, the question is whether or not this is related?
Ton...what article? We hide these 2 products until launch...and they shouldn't work.
The article is https://support.mozilla.org/en-US/kb/firefox-os-faq . The issue is that the AAQ link obviously depends on the client (its result that is). Shouldn’t it be disabled for any browser?
If you also go to support.mozilla.org on the geeksphone, click AAQ on the sidebar, you get the same issue.
I see now. This will be fixed soon when we make it live again. Although unfortunate, I don't think that we should invest time on finding a workaround for the time being. Thanks for reporting though.
You need to log in before you can comment on or make changes to this bug.