Welcome to the BrightGauge Enhancement Forums
The Enhancement Forums is one of several listening posts used to bring enhancement ideas to the ConnectWise Product Management Team. We utilize information from support tickets, information gathered from our onsite Consulting Team and our Sales Team during the sales process, as well as one-on-one or group discussions with our partners.
Do you have an enhancement you want to suggest or have you come across an enhancement you would like our Product Management Team to review? Vote and leave a comment. The more information gathered on the enhancement, the easier it is to make the case to the Product Management Team. The Product Management team automatically reviews enhancements with 250 votes or more and we will provide any updates to that enhancement as they become available.
Want to know what the statuses mean? Click here or on the "Status Legend" in the Links section.
Show your support for the ideas you like by voting and leaving a comment.
Now get out there and make your voice heard to help BrightGauge grow your company!
Ability to report on Retired assets in ConnectWise Automate
We'd like the ability to report on retired assets in Automate. We have a client that requires information on historical assets, but these don't pull into BrightGauge
Add site_name as field on Configuration dataset.
Brightgauge support aren't able to pull through the Site at this stage as they're "not accounting for an endpoint in our API calls that would correlate to the Site". Support has suggested that I create a partner request for this to compliment their own feature request.
Increase 300 character limit for Time Entry notes pulled from PSA
I would like to pull more than 300 chars, ideally 1,000, from Time Entry notes. This is because we want to pull specific time entry notes into customer facing reports being generated from BrightGauge, as this saves us a lot of time adding the text manually into reports.
I have been told that BG is not limiting the chars and it is the PSA API, however I figured worth raising on here because the direct impact of this is data coming into BG.
Customer Mapping for Dashboards like Reports
I'd like to be able to create dashboards and share with customers, however relying on a board filter is not good enough to ensure the data is limited to the customer. All it takes is for someone to change the dataset to alter the filters capabilities.
If the option to select the customer for a dashboard was like we do for reports via client mapping, it would be more secure.
Add Variables!
It would make a lot of my gauges easier if there was a design option to use specific variables without having to manually adjust numbers every time certain things change. For example: %customers% would be the total number of customers and %endpoints% would be the total number of endpoints. Even just letting me define a value for %placeholder% so I only need to make one change would be very useful.
Create parity datasets with NinjaOne, like Automate
NinjaOne API exposes all information needed to make a parity datasets that present the same information as Automate.
Please use the relevant NinjaOne endpoints to pull all device information:
- /v2/devices-detailed
In particular, I'm at least looking for memory statistics, which don't exist in any NinjaOne dataset.
Image Rendering
Currently it is SO painful to do this.
You cannot see the uploaded image from the selection so if you have more than 10 images stored....good luck finding the one you need.
Also and most frustrating is trying to scale an image so it does not crop too much or too little.
It is a battle of trying to manipulate a poor interface to get it to render right...And each time you try, you need to create a report, then try again etc.
Painful!
Format Axis to match Dataset Design
We would like to be able to format the X- or Y-Axis in our chart graph gauges to match the Dataset design - if it's set as a % or $, to be able to format the axis to be the same. For example currently, if we are using a % for data across a period of time, we have a 0 to 1 scale on the Y-axis and the time on the X-Axis. This causes some confusion for clients or colleagues who may be viewing the gauge.
Add field in Service Now Tasks Dataset to pull through the “Reason” field of the ESC (Escalation) records
Add field in Service Now Tasks Dataset to pull through the “Reason” field of the ESC (Escalation) records
Customer support service by UserEcho