Feature Requests

The request is the same as https://mspbots.canny.io/feature-requests/p/next-ticket-filters-multiple-filters-on-next-ticket , but for Autotask version

Add a function or settings that removes the last sync time below the widgets

We are requesting support for custom aggregate calculations. A specific example provided is an aggregate function that removes the maximum and minimum values in a column and calculates the average of the remaining data. This feature would allow users to address scenarios where outliers significantly impact results.

I need to lock down or at the very least control what tickets are shown for a small sub-set of my techs. For example, there are certain techs that should only see tickets with an "estimated hours" in Autotask that is under 1.0 hours. Can you point me in the right direction on how to set that up and how to move people in and out of that. Thank you Also is there a way to show Estimated hours on the next ticket template as per the attachment? One other question. Is it possible to have the Ticket Estimated Hours show up in the filter list as per my second attachment?

To be able to adjust the column width of table widgets in order to fit horizontally in a report/dashboard. Without this, table widgets in a report cannot be viewed in full view.

Please include the calculation options as draggable icons when creating a calculation layer. This was something that was in Brightgauge and was a simple and convenient.

Client has requested for bot to be able to tag a team ex. @Help Desk Team

Is there anyway I can lock the location of a Widget on a dashboard so when I add new Widgets all other widgets don’t get moved around?

We are requesting to have the ability to “ignore” or “snooze” failed API calls on the integrations. For example, the integration is setup correctly but the API is attempting to access modules within the software that we do not use, therefore the API calls are failing consistently. During our onboarding calls, the trainers said these particular items will continue to show as failed all the time yet they are training us to always check the integrations for issues before creating a widget or a bot. It would be nice to be able to ignore or snooze those failed API calls that are known to not be working for whatever reason instead of showing up all the time as an issue.