-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Bug] Reporting Fenix webcompat issues in app goes to Fennec team, then gets closed #1256
Comments
I think we need to identify Fenix issues in some way. It would be great if we could pass flags to send the build number and browser app_id with the report. |
Did you talk to webcompat about this?
|
@colintheshots do you have an example of an issue that got closed? I checked with the web compat team and they’ve been triaging fenix issues and if one got closed it might have been a mistake or a bug |
webcompat/web-bugs#27257 (comment) The issue got sent from Webcompat to Fennec and closed as can't repro basically. |
Hey there! @colintheshots did you report the issue you linked via Fenix' embedded Report Site Issue thingie? |
Yes, that's exactly how I reported the issue. |
Ah, nevermind. I just tested the reporting, see webcompat/web-bugs#28961 - and it worked fine, so I was confused. However, as it turns out, we didn't add support for that on our side right away (we have to whitelist labels that can be set via URL parameters to avoid abuse). We did that in webcompat/webcompat.com#2820, which got deployed on 2019-03-14 - so all reports after that will be tagged with a Fenix tag. I have reopened the web-bug mentioned here, and I didn't find any other issues reported by you. If there are more issues that got closed, please let us know (#webcompat on IRC or Slack), and we will reopen those! Sorry for the confusion. |
Thanks @denschub ! |
Steps to reproduce
Open an issue using the "Report an issue" link.
Expected behavior
The issue is appropriately checked against Fenix.
Actual behavior
The issue is incorrectly checked against Fennec and Focus.
Device information
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: