UserReporting integration data is limited

Unity Services
, ,
1

I am wondering what is the purpose of having such integration if the data that is being forwarded is being tremendously limited?

Right now the data contains:

  • Identifier
  • Project Identifier
  • Summary
  • ReceivedOn
  • ExpiresOn
  • GeoCountry

with some empty placeholders such:

  • IsSilent
  • ThumbnailDataBase64

I think that the power of such integration comes from the possibility to process the data (in this example, the UserReport data) on the other end. Right now, because of the lack of any CloudDiagnostics rest api integration is pretty much limited only to creating the link for the actual UserReport in the Unity Dashboard. Is that intended behavior?

2

I would second this and ask that the team work on improving the built-in integrations.

For example, Trello tickets created from a user report only use a single field – the report summary plus providing a link back to the Unity Dashboard. This leaves teams trying to use these integrations in a lurch – basically needing to constantly go back to the Unity Dashboard when the point of the integration is to get these reports into a separate workflow system.

Huge +1 here!