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
We need an ignore button to mark nodes ignored. Users requested this because some of our scans report false positives. The button must log when an issue is ignored or unignored, similar to how a node is logged equalified or unequalified.
The ignore action should be done on a single property page, since it is a universal action.
We discussed either included a list of nodes on the property page, or a search that allowed you to search for nodes and add them of a list of ignored nodes. You should be also able to remove them from the ignored list. It may be helpful to include the time when a node was ignored.
That UX may be changed in Version 2.
The text was updated successfully, but these errors were encountered:
We started to discuss this in #323. We decided not to include the explanation because it's seemingly penalizing users for using a feature. We don't want to create anti-user features like that. Plus, the user will have a record of when things were ignored or not.
We need an ignore button to mark nodes ignored. Users requested this because some of our scans report false positives. The button must log when an issue is ignored or unignored, similar to how a node is logged equalified or unequalified.
The ignore action should be done on a single property page, since it is a universal action.
We discussed either included a list of nodes on the property page, or a search that allowed you to search for nodes and add them of a list of ignored nodes. You should be also able to remove them from the ignored list. It may be helpful to include the time when a node was ignored.
That UX may be changed in Version 2.
The text was updated successfully, but these errors were encountered: