Would like to see the capability to create a filter which looks for key words in the customers name and will then list all devices including devices at the customer sites. The filter Device -> Customer -> Contains -> 'Key word' Will only list devices at the customer level, not devices at the site level. The filter Device -> Customers with Sites Does not have the contains option. Only 'Equal to' or 'Not Equal To' ...more »
For a while we allowed the ability to Manage services which then allows technician to among things Disable services. Now we sit in the situation that we want to have a report of all services which are currently Disabled, but the Filters in N-central does not allow this. When creating a filter we have: Monitoring | Has at least one service in status | Equal/Not Equal To ------- and then every variant (failed, warning...) ...more »
Allow admins roles or other user to take ownership of existing filter, when administrator are no longer with a company, retired.
ownership of filters should be interchangeable to avoid a large clone structure of duplicates.
We can currently create a filter based on Warranty Expiry Date before/after a given date. I would like a filter for devices that are MISSING warranty information.
Right now it's possible to filter a report by customer, but not by site.
The only way around this would be to filter by a rule and then we would need to create a rule and a filter for that specific site's devices
But why not being able to see in a report for a customer the respective sites where a device is included in?
Or why not being able to filter by site?
It would be helpful for more filters to be available one the reports page, for example sorting tickets by completed date and so on. The limited number of filters seems like an oversight.
It would be great if our N-Central users could create personal filters without assigning them the filter manage permission.
Maybe add another permission level to Filter.
I want to be able to see what Rules, etc are dependent upon a given filter, template, etc.
ie, if I delete a filter, I see a prompt that I shouldn't do that if there are associated rules, but there's no way short of examining *every rule* to know what the associations are.
Because I have hundreds of filters but only perhaps a half dozen of them do I use for patch management filtering.
It's a must that you can save filters for Opportunities.
I don't want to set them every time I'm working with Opportunities.