Open Bug 1843509 Opened 1 year ago Updated 1 year ago

suggest_sponsor and suggest_non_sponsor are in metrics.yaml but can't happen?

Categories

(Firefox :: Address Bar, defect, P3)

Product:
Firefox
Component:
Address Bar
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox-esr102 --- unaffected
firefox-esr115 --- fix-optional
firefox115 --- wontfix
firefox116 --- wontfix
firefox117 --- wontfix
firefox118 --- fix-optional

People

(Reporter: mak, Unassigned, NeedInfo)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [sng-scrubbed][search-tech-debt])

These were introduced by https://hg.mozilla.org/mozilla-central/rev/3179b109bcf2 and removed by https://hg.mozilla.org/mozilla-central/rev/02147a101bd9ce16c305aab7e25c0267cdcb0f3d

It looks like they can't happen anymore and thus should be removed from metrics.yaml
We should also somewhere keep a changelog for Data Science when these lists change.

We could use the Commentary field
https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/urlbar_engagement

Set release status flags based on info from the regressing bug 1829081

:adw, since you are the author of the regressor, bug 1829081, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

status-firefox115: --- → affected
status-firefox116: --- → affected
status-firefox117: --- → affected
status-firefox-esr102: --- → unaffected
status-firefox-esr115: --- → affected
Flags: needinfo?(adw)
Whiteboard: [sng-scrubbed][search-tech-debt]
Severity: -- → N/A
Type: task → defect
Priority: -- → P3

Set release status flags based on info from the regressing bug 1829081

status-firefox118: --- → affected
You need to log in before you can comment on or make changes to this bug.