You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to propose a feature that enhances the user experience when dealing with false positives in the AdGuard DNS Personal query log. Currently, reporting false positives can be cumbersome, and a more streamlined approach would benefit users.
Proposed solution
Add a button labeled "Report False Positive" in the expanded query window of the Personal query log, positioned next to the "Add user rule" button.
Additionally, include the "Report False Positive" button in the 3-dot menu on the query log landing page.
When clicked, both buttons should link users directly to the appropriate support page for the filter that caused the false positive.
Examples:
For users utilising the hagezi filter, the button would link to: hagezi GitHub Issues.
For users of AdGuard's own filters, the button would link to: AdGuard Report Issue Page.
Alternative solution
An alternative could be to implement a context menu option that allows users to report false positives directly from the query log without needing to navigate away from the page. However, the proposed button solution is more straightforward and user-friendly.
The text was updated successfully, but these errors were encountered:
Issue Details
I would like to propose a feature that enhances the user experience when dealing with false positives in the AdGuard DNS Personal query log. Currently, reporting false positives can be cumbersome, and a more streamlined approach would benefit users.
Proposed solution
Examples:
For users utilising the hagezi filter, the button would link to: hagezi GitHub Issues.
For users of AdGuard's own filters, the button would link to: AdGuard Report Issue Page.
Alternative solution
An alternative could be to implement a context menu option that allows users to report false positives directly from the query log without needing to navigate away from the page. However, the proposed button solution is more straightforward and user-friendly.
The text was updated successfully, but these errors were encountered: