To understand the purpose of enabling API in the configuration page of Surveys for Jira Service Management (Surveys for JSM) settings.
To understand how data is stored and who can modify the Surveys for JSM data.
To understand the limitations of the Surveys for JSM app.
Surveys for JSM uses a webhook to trigger an action (sending an email with a link to a survey) when a “condition” (set in Automation by Jira) is met. The app generates reports based on the surveys answered by the customers – this data can be pulled through the usage of API.
The users are unable to modify data using API. Surveys for JSM metadata properties cannot be modified via API.
There are no limitations on the condition to trigger the survey. The user can create different conditions using Jira automation.
Atlassian API is used to get information about Surveys for JSM users . Only the user ID is stored.
The user ID is stored so that the app is able to make requests to the Atlassian API. The app gets the name of the user and displays it on the Survey Report page and the Review Survey sidebar.