Once you have installed the app, you are able to create Fabulous Surveys for your Jira instance.
...
...
Field | Value | Description | ||
|---|---|---|---|---|
Recipient | Reporter (default) Assignee | The email recipient will be taken from reporter, assignee or | ||
Rating type | Stars (default) Smiles Numbers Link | Rating type will be used as part of the email body instead of mask     | ||
Rating size | From 5 (default) to 10 Applied only for: stars, smiles or numbers | Rating size will be used together with selected rating type as part of the email body instead of mask | ||
Rating color | Black, Blue, Coral, Cyan,Deep Pink, Green, Red (default), White, Yellow Applied only for: stars, smiles or numbers | Rating color will be used together with selected rating type as part of the email body instead of mask | ||
Email subject | Text: default value → | The subject of the survey email. Also, the next masks might be applied inside: | ||
Email body | HTML: default value ->
| To build the body of the survey email, you can use base HTML tags as |
...
Field | Value | Description |
|---|---|---|
Question | Type text | Question for the survey form |
Required | Type toogle | If required selected, the question answer should be provided to submit the survey form |
Active | Type toogle | If active selected, a field will be displayed. Has priority under the required. In case of required=true and active=false field not be displayed so the form will be submitted. |
Type | Type Select Radio, Checkbox or Text | Type of the question. Checkbox → multiple applicable answers from the options list. Text → input field text for the answer. |
Add option | Type Button | For the Radio type at least two options should be provided For the Checkbox type at least one option should be provided For the Text type option will not be applied. |
Option | Type Text Applied only for: Radio or Checkbox types. | Option for the corresponding type. |
Delete option | Type Button | Delete option from the list |
...
The campaign SMTP configuration overrides the global or the default SMTP configuration. Please check the next examples to understand how this section works.
GIVEN -> The global SMTP configuration is a DEFAULT. WHEN -> created a new campaign its SMTP configuration also will be the DEFAULT. THEN -> the global configuration changed to the custom one, but the campaign configuration was left in the DEFAULT.
GIVEN -> The global SMTP configuration is a CUSTOM (on the campaign level it's called a GLOBAL). WHEN -> created a new campaign its SMTP configuration will be a GLOBAL. THEN -> the global configuration changed to some new value, in that case, the SMTP campaign configuration switched to the CAMPAIGN state, as its value is different from the DEFAULT and the GLOBAL.
Regarding these examples, you may notice that the campaign SMTP configuration copies the value from the global SMTP configuration when it's created and store this state until it will be changed directly inside the campaign.
The campaign SMTP configuration might be in the three states: CAMPAIGN, GLOBAL, or DEFAULT. The state can be downgraded from the CAMPAIGN to the GLOBAL (if the global config exists) or to the DEFAULT by clicking a Delete button.
...
The campaign also can be upgraded to the GLOBAL state if it’s state the DEFAULT and the global config exists by clicking Upgrade to global button.
...
| Note |
|---|
PLEASE NOTE The expiration time stored directly as part of the survey link (in JWT token), so changes in the expiration time section have affect only for the survey link before it was sent. |
Direct
| Anchor | ||||
|---|---|---|---|---|
|
In this section, you can switch on/off direct on-site surveys without email notification. The link for the configured surveys will be available from the issue interface. Email, SMTP, Trigger and Periodicity functionality will be ignored. Please note: only one answer per survey per issue can be left for this mode.
If the issue already has an answer for the survey campaign even if it was answered by the email link, the direct mode survey will be calculated as passed. Also in this mode can be added a workflow condition, to restrict moving an issue to some status until survey(s) is/are not passed.
Configuration:
Switch to the tab Direct into the Campaign configuration interface and switch on the direct mode, press Save:
...
The campaign from the campaigns list will be marked with ON SITE label.
...
Go to: Configuration → Issues → Workflows → Your project active workflow → Edit
...
Select: Diagram → Arrow for the status where will be restricted to move without direct survey answer → Conditions
...
Select Add condition.
...
Select: Survey allow go to condition and push Add button.
...
Check that condition in the list, and push Publish draft button:
...
Using:
Go to the project issue and push Answer on surveys button:
...
In the list, you can see the surveys campaign which should be passed to unlock ticket movement into review status. Select the survey link from the list and finalize the survey. It will be opened in
the new tab.
When the survey will be completed, reload the issue page. The surveys list should be empty, the answer should be added to the Activity screen, and movement to the issue status will be available.
...
| Note |
|---|
PLEASE NOTE: Only one answer per survey per issue can be left for this mode. |
View Permissions
| Anchor | ||||
|---|---|---|---|---|
|
...
For every section available one of the 3 options:
Admin (default) → only users who had the role '
ADMINISTER_PROJECTS' can have access to the page or functionality.All → any Jira user can have access to the page or functionality.
Users → only users defined in the corresponding list can have access to the page or functionality.
Users for survey Custom Field
| Anchor | ||||
|---|---|---|---|---|
|
...