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
If you know where the problem lays indicate it:
Faraday Server (Web UI) Dashboard
Steps to reproduce
On adding new columns to the vulnerability table, The scroll bar isn't effective and the new columns are hidden. (A resizing of the existing columns has to be done)
Adding new columns to the view also is only pertained to the particular session and is not visible when the user logs in from a different browser
Example:
As a faraday admin, I enable policyviolations column to be in view and remove tags columns,
Alice as a pentester logging in still has to manually add policyviolations column in order for her to view (By default a set of columns are loaded and new changes are not persisted)
Note: Currently in the Corporate trial we have two users
Expected results
The scroll bar at the bottom should enable scrolling across various columns, instead of users having to resize existing columns
OS
Windows 10 (Host OS)
Provide information on your operating system. Example:
Hello @Thilaknath
This ticket is not referring to a bug, it's a feature request.
We will talk with the developers team in order to see if this could get added to the roadmap.
We are currently working hard to release a new version of faraday soon.
Cheers.
Issue Type
Faraday version
C-3.2
Component Name
If you know where the problem lays indicate it:
Faraday Server (Web UI) Dashboard
Steps to reproduce
Example:
Note: Currently in the Corporate trial we have two users
Expected results
The scroll bar at the bottom should enable scrolling across various columns, instead of users having to resize existing columns
OS
Windows 10 (Host OS)
Provide information on your operating system. Example:
$ cat /etc/lsb-release
DISTRIB_ID=Kali
DISTRIB_RELEASE=kali-rolling
DISTRIB_CODENAME=kali-rolling
DISTRIB_DESCRIPTION="Kali GNU/Linux Rolling"
The text was updated successfully, but these errors were encountered: