-
-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request - customizable columns in the agent list #308
Comments
So you mean a column where you can select from a drop down list different options one of them being the IP address of the machine? |
Sure, however it could be best implemented. |
Agree, customizable columns would be very helpful. Not that you are trying to copy the major players, but for example Kaseya, N-able and Labtech all implement 'views' where you can choose which database fields you wish to see, whether these fields should have any particular filters applied to them, etc. You can save these views and easily switch back and forth between them, allowing you to quickly bring up a (potentially filtered) list of the machines you want to work with, along with the relevant fields from the database. It's super powerful. Example view: Workstations missing Windows updates |
#219 Merging with this request |
+1 OS name and ip would be really helpful to have on Agent List view. |
I TOTALLY agree! It would be really helpful to see if a client are connected from home (in VPN), filtering the public IPs of the 2 offices... |
This would be really handy, especially for adding custom fields to the agent table! |
We are also very interested in displaying custom fields on the agent table. In general, of course, to be able to edit the agent table. |
Step 1 is done, customizable columns library: amidaware/tacticalrmm-web#9 Next step is putting it into the agents table, and then adding custom fields into selectable list |
One particular my guys mention is the LAN IP address. That would be very helpful to be able to display that without clicking on the agent?
The text was updated successfully, but these errors were encountered: