Does a specific reported data anomaly on Baresquare start to ring bells? The related incidents feature can help you refresh your memory and trigger an action faster.
Assume you see an interesting data anomaly on a Baresquare ticket.
And you try to remember when the last time was that something similar happened.
And how did you deal with it? Was this resolved and how/by whom?
Baresquare can help you with this!
Any ticket on our Platform can be related to one or more tickets. This check is done in the background and you can view the results by clicking on the 'Related incidents' tab.
There, you can check the full history, and recall what and how a resolution action was performed (or wasn't!)
Hint: if no related tickets have been identified, the tab will read zero inside the parentheses.
For two incidents (tickets) to be related, all of the following conditions must be met:
the two incidents share the same key metric
the two incidents share the same sentiment
the two incidents share the same flow value
the "child" incident contains (at least) all dimension values of the "parent" incident
the "child" incident contains (at least) all labels of the "parent" incident