Welcome to the BrightGauge Enhancement Forums

When filtering on dates using Dashboard Filters, there is no option to specify a custom date range, despite there being an option for this in the Gauge Editor

We need to be able to report on who the referral is on opportunities within BrightGauge. I was told this is not part of the Opportunity Dataset and that it can't be added.  How are we to use BrightGuage and report on this data?  The only option is "referral flag" which is meaningless to being able to report on referrals made by individuals to track opportunity results.

Please escalate this request.

Currently there is a gauge that is called Sophos MDR Threats. This gauge is just open alerts in Sophos, and has nothing to do with actual threat hunting or MDR created tickets. This gauge should be renamed to something like Sophos Alerts.

If it is possible could you please pull the actual Sophos MDR tickets opened per client into Brightgauge that would be very helpful in client facing reports, and for QBRs/vCIOs.

I have individualized daily Reports I send to each Account Manager -- I was able to use a Template to create these, but making changes or updates to the Template does not change the Reports it created; I have to update every one individually every time I change anything. Having a Parent/Child relationship between Templates and Reports created from them would make that feasible.

Having been told recently in our BrightGauge kick off and implementation meetings that a simple client level request could be made to increase any dataset and that the current ones were just the defaults. This turned out to be false and CW Support have told me to raise an enhancement.

For example. The dataset Ticket Statistics Last 240 Days, this isn't even a year of ticket data that for many is the bare minimum to get useful reporting and ticket trends.

I think there shouldn't be any limitations 

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.   

When exporting a gauge to a CSV unless it's a list gauge the headers are lost. Please allow all headers to be kept in the format. 

Please add the ability to use wildcard filters at dashboard level.

CUurrenlty, we can use wildcard filters on gauges, but not on dashboards.

eg:  Service Board like %ervice%

It's mildly frustrating to have all gauges/values locked to the global color palette setting. I (and I suspect others) would like the ability to manually change the color of any gauge or value on the fly. I know we can sort of do this with a threshold, but that doesn't recolor the legend and so causes confusion. 

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.