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!
Dynamic Date Filter: Add After (n) Days (we already have 'Earlier than (n) Days', it should go both ways)
On past-looking data, we can use 2 filters to achieve a specific, custom range: Last (n) Days // Earlier Than (n) Days Ago
This solution works for looking at date ranges in the past.
BG has Last (N) Days, Earlier than (N) Days, within Next (N) Days, but does not seem to have After (N) Days. I would expect that to be there since it is very similar to the Earlier than (N) Days filter.
I will start with the past-looking metric to explain better:
- Past-Looking Data
- Need: Opportunities where date_became_lead is between 90 – 180 days ago
- Solution:
- Filters:
- Filters:
- Date_became_lead = Last (n) Days {180}
- Date_became_lead = Earlier Than (n) Days Ago {90}
- The combination of these filters yields a list of opportunities created between 90 – 180 days ago, which achieves the purpose.
- Forward-Looking Data
- Need: Opportunities where expected_close_date is between 90 – 180 days in the future
- Solution:
- Expected_Close_Date = Next (n) Days {180}
- Later Than = FIXED DATE
- The combination of these filters yields a list of opportunities closing within the next 180 days and which are also after a fixed date;
- We need this to be dynamic, like it is with the past-looking/”earlier than” data.
Meraki Firmware Upgrade reporting
Allow reporting on upcoming Meraki firmware upgrades.
API module: Get Organization Firmware Upgrades - Meraki Dashboard API v1 - Cisco Meraki Developer Hub
Abillity to customise report name
At the moment we have no power over the name of the PDF report in BrightGauge. We'd like to be able to use a variable as the start of the PDF title, the report name, and then append free text where needed
Something like
240919 - Monthly Service Report - v1.0
[variable] - [variable] - [free text]
Dataset for Datto RMM statistics on Antivirus, Defender, and EDR deployments
The Datto RMM datasource does not currently have any datasets that support reporting on the status of deployed security products/features such as Windows Defender, Antivirus, and Datto EDR. Please consider adding this so we can provide a more complete overview of device compliance other than just Patch Management.
enable auditing on dashboards
all changes to all part of the system should be audited. gauges, reports, dashboards - everything.
VSA X
We'd like to see Kaseya VSA X integration within BrigtGauge. We depend on using BrightGauge for dashboards and sending reports to clients, but as we move on to VSA X from VSA 9.5, we are losing this ability.
Header Notes in Projects for Brightgauge
We desperately need the ability to add the "Header Notes" field to our project reports in Brightgauge. We store important information to share with the team. This is a standard field, why is it not included by default?
Gauge level security & User restriction
Currently, the only way to restrict specific gauges is by restricting datasets at the user level and I need the ability to secure gauges and limit to specific users without restricting the data set as the data set in question is used by other members of my team.
The request is
Customer support service by UserEcho