Messages from mobile nightlies are being shown on production

RESOLVED FIXED in 2.0

Status

Input
General
P2
normal
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: aakashd, Assigned: davedash)

Tracking

Details

(Reporter)

Description

7 years ago
Steps to Reproduce:
1. Go to http://input.mozilla.com/en-US/search/?q=&product=mobile&version=&date_start=&date_end=
2. Look at messages from "maemo" devices
3. Select the 1.1rc1 version
4. Select the 1.1b1 version

Actual Results:
Messages are shown under "All", but not under the last betas. The messages seem to be coming from our nightlies since they are being registered as "Maemo" (i.e. user agents are correct). Me thinks the version switch from 2.0b2pre to 4.0b2pre on Fennec two days ago might be the culprit.

Expected Results:
Only messages from the latest beta should be shown on the production dashboards
(Reporter)

Updated

7 years ago
Priority: -- → P2
Target Milestone: --- → 1.9
I don't think I agree with the expected results here. If you search for all versions, it shouldn't be surprising that indeed feedback for all versions is shown.

What's confusing here though is that we don't have 2.x (or even 4.x) in the product details database yet:

http://viewvc.svn.mozilla.org/vc/libs/product-details/history/mobileHistory.class.php?view=markup

If this data is inaccurate, it needs to be fixed (I can do that, if someone tells me what data points need to be added there). Then these versions will soon show up in the list.
I'm surprised that we're even accepting feedback from those specified betas.  We were unsuccessful in receiving feedback from Maemo devices on stage until we flipped the ENFORCE_USER_AGENT value in settings_local.py from True to False.  Could that value currently be set to True in production?
Unless I am on drugs, we are accepting feedback from everything >= (what we consider the latest beta). That'd mean, we do accept 2.0b1 if we consider 1.1rc1 the latest.

If Maemo devices are rejected in general with the enforce flag on, we should fix that bug.
(Reporter)

Comment 4

7 years ago
Yeah, (In reply to comment #1)
> I don't think I agree with the expected results here. If you search for all
> versions, it shouldn't be surprising that indeed feedback for all versions is
> shown.

Aye, but just like with the Desktop Firefox dashboard, the intent here is to only show feedback from betas. We should just remove "All" entirely from both dashboards.
(Reporter)

Comment 5

7 years ago
Going off of the previous comment...we should, at the very least, only show beta-specific feedback on our dashboards (just like for Desktop Firefox).
Aakash says to just take out "ALL" and show the latest beta by default.
(Reporter)

Comment 7

7 years ago
+1 and also for Desktop Firefox, so it's not confusing.
So, just so I'm absolutely clear: we still want mobile nightly submissions to show up on http://m.input.stage.mozilla.com, but not on the desktop version, right, per 600355?
(Reporter)

Comment 9

7 years ago
Good point, here's the total answer:

Production
* Only show feedback from users on the betas
* Default to latest beta and do not show "All"

Staging
* Only show feedback from users on the betas
* Default to latest beta and do not show "All"

Even though Feedback is not on Android in Beta 1, those users can still send feedback just by goign to the URL of the submission pages.
Flags: in-litmus?
(Reporter)

Comment 10

7 years ago
When I filed this bug, I was hoping Beta 2 (i.e. Input on Android Betas) would be out. It's not and it's better to show nightly submissions in the meantime. Moving this back to 2.0 when I hope Beta 2 for Mobile Firefox will be out.
Target Milestone: 1.9 → 2.0
4.0b2pre should be in the Version drop down once Product: Mobile is selected.

Currently I have to select p:mobile v:All to see Fennec Android nightly input.
(Reporter)

Comment 12

7 years ago
We're going to neglect nightlies as official versions under product as this dashboard is only for beta feedback. I'll be posting out more information via a blogpost on how this stuff is all meant to work soon, Austin.
I *think* this might be fixed with the faceted search patch, which now specifically picks out the latest beta's data. Is that right, Dave?
Assignee: nobody → dd
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED

Comment 14

7 years ago
in-litmus+: https://litmus.mozilla.org/show_test.cgi?searchType=by_id&id=13717

Updated

7 years ago
Flags: in-litmus? → in-litmus+
Component: Input → General
Product: Webtools → Input
You need to log in before you can comment on or make changes to this bug.