Prepopulate theFirefox Versionfield for Nimbus

[AnaMedinac]

Is it possible to pre-populate the Firefox Version field in the rapid experiments form with the current Firefox Version. This way it's automatically filled in and the user doesn't have to worry about this field unless they're concerned with the version.

┆Issue is synchronized with this Jira Task
┆Issue Number: EXP-193

[jaredlockhart]

@AnaMedinac Right now there's no way to determine what the 'current firefox version' is inside Experimenter, so if you wanted it to behave that way I'd suggest sticking a placeholder in that literally says 'Current Version' and links out to the release calendar.

Side note, I'm confused about what this field does. Is it the minimum or maximum version? Does it correlate to the channel specified in the audience?

[jaredlockhart]

Let's close this and go with users being intentional about which specific versions they intend to target.

[pdehaan]

(formerly #3043 (comment))

Currently looks like:

I think my concerns are if Firefox 83 is release, we'd have ~6 old builds at the top of the list that don't make sense. Or each new experiment would always have to select the correct Release version from a dropdown. Or if you mistakenly select "Firefox 94.0" from the dropdown (because reasons), the experiment would launch (if not caught+rejected by an operator), but nothing would happen because even after your enrollment+test period, that version would never be in scope and you'd presumably get no results back.

But yeah, maybe its too tricky to scrape the list of current trains from https://whattrainisitnow.com/ (or the upstream https://product-details.mozilla.org/1.0/firefox_versions.json which is where they apparently fetch from). Having a pseudo-dynamic list of dropdown values adds a lot of weird edges.
I just didn't know if a select list with only 3 options:

• "Release Firefox 78.0"
• "Beta Firefox 79.0"
• "Nightly Firefox 80.0"

... would make it easier an easier UX for experiment submitters. Since we only ever show 3 options, "Release" would always be the first/default option and what submitters would want 99.99% of the time anyways.

[jaredlockhart]

Blocked on design input from @AnaMedinac and @k88hudson

[k88hudson]

I agree with @AnaMedinac's original comment that we should set the default value to the current release. I think it would also be good to indicate that in the UI as well (maybe the words "current release"?).

What other design input are you looking for, or are you just looking to reconfirm @jaredlockhart? Would it be doable to read that value from https://product-details.mozilla.org/1.0/firefox_versions.json?

[k88hudson]

@k88hudson I will discuss options with @jaredlockhart in our next pairing session