Customers have concern about the way they can self-troubleshoot.
Request: "We have a few cases where it seems that either a person or the system is changing the mapping for some of our projects that link up to Salesforce, and its causing some havoc. Unfortunately, the JIRA logs don't pick up these tweaks (or so it seems), so I was wondering if you had any way to see what may have been going on."
Case Reference: https://servicerocket.desk.com/web/agent/case/60578
Having a tool allowing administrators to analyse problems is mandatory, Ican't understand how your customers can't work without this. For nowServiceRocket connector is a black box, and as a system admin this is notacceptable, we waste a precious time to analyse mapping issues.
It's absolutely necessary to provide an equivalent of the diagnostics menuwith the cloud connector. Your customers must be able to do quick analysisif mapping errors occurs without having to create a support ticket. Can youescalate this need to your product team ?
You won't be notified about changes to this idea.