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!

+2

Gauge search info: Add last used to ID gauges that have not been used in X months.

Dustin Morse 8 months ago 0

We have over 30 pages of gauges and 10 people across the organization that are creating gauges (Leadership, Directors, Managers). I can guarantee that there are duplicated gauges and gauges that were created years ago that haven't been used. 

I know I can filter by unused as well as last updated but that doesn't give the full picture. It could have been last modified and last used a week ago. 

I want to be able to filter based off last maintained AND last used (on a Dashboard/Report/Goal) was 6+ months ago. Having a last used field that would be updated daily would be beneficial. 

+2

Access to Quickbooks Data

Abby Lynch 9 months ago 0

I was under the impression that I had virtually unlimited access to tables and fields in on-premise applications such as QuickBooks with Brightgauge??  The first attempt at a gauge I attempted was for my retail division... to show daily sales by payment method (Cash, Credit Card, Check, etc.)... no such fields are available.

These limitations are very crippling and disappointing with this otherwise potentially impressive product.

Back to the drawing board with the horrible QB Advanced Reporting Tool, which is similar to PSA Report Writer, which I assume I will also have to use for a lot of what I still need out of PSA as well.... we will see.

+2

Increase 1000 row limits

Vidal Garza 10 months ago 0
+2

Dataset sync alerts

Jeremy Baxter 10 months ago updated by Shane Wright 7 months ago 4

Hey team, would like to be notified anytime a dataset sync interval is missed 

+2

Create parity datasets with NinjaOne, like Automate

Brandon Fox 12 months ago in CMS 0

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.

+2

Include created_by field in CW Manage Invoice Data dataset

Kev Penny 1 year ago 0

The Invoice Data dataset contains fields like updated_by and adjusted_by, but not created_by, which seems like a big oversight. We need to be able to report on who created invoices, and the workaround we've been given is to create a custom field, which would rely on someone manually setting that every time they create an invoice.

+2

Retention Policy For Sent Reports

Brent Le Cornu 1 year ago in Fortify 0

We believe there is a current security and compliance issue with the unlimited retention of reports in the "Sent" reports section. There is no way to automate their deletion after a given time, and no way for BrightGauge support to do it in our behalf. The only method we have found is to manually sort the "Sent" reports in ascending order by age, select all (applies ONLY to the current page), delete, repeat... This is unmanageable, and even if we use a macro recorder to complete the task, we still have to manually set it to run and then watch it to make sure it doesn't delete files inside our chosen retention time.

+1

"Earlier than (n) Months Ago"

Mike Buonaspina 4 weeks ago 0

Filter for dates should have an "Earlier than (n) Months ago" for monthly snapshot data scenarios. 

+1

Dynamic Date Filter: Add After (n) Days (we already have 'Earlier than (n) Days', it should go both ways)

Micah Nichols 1 month ago 0

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:

  1. Past-Looking Data
    1. Need: Opportunities where date_became_lead is between 90 – 180 days ago
    2. Solution:
  1. Filters:
  2. Filters:
        1. Date_became_lead = Last (n) Days {180}
        2. Date_became_lead = Earlier Than (n) Days Ago {90}
        3. The combination of these filters yields a list of opportunities created between 90 – 180 days ago, which achieves the purpose.
  1. Forward-Looking Data
    1. Need: Opportunities where expected_close_date is between 90 – 180 days in the future
    2. Solution:
        1. Expected_Close_Date = Next (n) Days {180}
        2. Later Than = FIXED DATE
        3. The combination of these filters yields a list of opportunities closing within the next 180 days and which are also after a fixed date;
          1. We need this to be dynamic, like it is with the past-looking/”earlier than” data.
+1

Ability to Customise "Legend" Text

Luca Whiteway 1 month ago 0

We would like the ability to customise the text in the "Legend" field when this is enabled on Gauges.

An example being that a gauge showing tickets in and not in a Waiting SLA has the text in the Legend stating "True" or "False". I would like to be able to rename this text so it is clearer, I.E. "Waiting" or "Not Waiting".