User Story (Required on creation):

As a developer, I would like to understand an incident cause straight away as part of the REST response instead of having to navigate to the root cause incident / the cockpit.

Functional Requirements (Required before implementation):

• Add "rootCauseIncidentMessage" (part of http://localhost:8080/camunda/api/cockpit/plugin/history/default/incident/) as output to the REST API for Incidents
• As a second Point:  Stacktrace (but that is maybe a problem of security).

Technical Requirements (Required before implementation):

Limitations of Scope (Optional): 

Hints (Optional):

The incidentMessage in the public REST API doesn't show the root cause incident message. When using call activities, the root cause incident message is not easily retrievable in a hierarchy of process instances. This is what we have the rootCauseIncidentMessage property in the private Incident Webapps REST endpoint for.