By default, all the standard fields (such as Summary, Description, and Components) and all the required fields from the Create Issue screen of the project will be shown during request creation in a Customer Case forum.
The ability to set up the required field is only available for team-managed projects. You can propel this feature for team-managed projects by adding your vote here. |
To add additional fields to the form, follow these steps:
Find a relevant Jira screen to apply this field
If the screen you apply a new field for is shared between multiple Jira projects, remember that a new field will also be used in these projects. How to check what projects use the same screen? Jira project → Project settings → Summary → Screens section |
6. Go to the Fields section
7. Find the relevant field name and select it
8. Find the custom field you've just created and set it as required
Now check the result. Your custom form on a portal may have the following look:
If your form has required fields except for Summary and Your email address, creating a request on the forum via email makes it impossible. |
At Stiltsoft, we added the Component field to our form on the Support Forum and set it as optional to let our customers create requests via our support email address. Each component corresponds to one of our apps.
Also, each component has a particular Assignee in Jira. In our case, it's a Product Manager responsible for an app.
Thus, when a user defines a component in a request, a ticket is automatically assigned to the relevant Component lead (Assignee).
Customer Case supports three types of user roles:
Customer Case uses Jira projects as a basis for storing the submitted requests. This includes the usage of the project's field configuration scheme. Presence of any required fields different from Summary, Description, and Component fields in the Create Issue screen of Jira will lead to the failure with request submission in Customer Case.
To avoid any issues with this, you need to make these fields as optional. For the details, please see Atlassian documentation.
Please revise your field configuration and leave only the Issue Summary, Description and Component fields as required for all your projects associated with forums.
You can place the public URL of your feedback forum on your websites, in your wiki system or embed into your application or product.
Other users of feedback forums can only see your first and last names, added comments and ideas, and ideas that you voted for.
The app doesn't provide the capability to hide the surnames of the forum participants. The reporters' names are fetched from their Atlassian account once leaving feedback.
Yes, you can. Please see the Creating an Account section.
You can become a watcher of the idea and receive notifications about all progress on the idea (new comments, status change). You become watcher of an idea automatically if you have created or commented it.
Each user is allowed to vote only once for the same idea. This is done to prevent false voting and spamming.
No, there are no limits for votes within the same forum. You can vote for any idea you like or want have in the product.
Yes, it is possible. Please see the Setting Access Restrictions for Forums section.
Removal of the feedback forum causes reset of votes. Ideas and comments from users will be preserved in JIRA. If you decide to restore the forum, all ideas will be restored, but comments and votes will be reset.
You can submit feature requests for Customer Case on its own Feedback Forum.
To enable categories for your feedback or support forum, you need to configure components for the JIRA project used for feedback forum.
For regulating the required or optional selection of the category during idea or request submission, you need to set the Required or Optional status for the Component field in JIRA.
When using a shared field configuration, your modifications in the status of the Component fields will be propagated to other projects associated with this field configuration. |
You may encounter such an issue with projects using the non-default permission scheme, for example, Service Desk projects. You shoud grant the following permissions to the atlassian-addons-project-access role or to the Customer Case for Atlassian Cloud user:
For the details on permission scheme management, refer to Atlassian Documentation. |
If you need to get the URL of the request in Customer Case when having JIRA issue key or ID, run the following request in your browser:
{customerCase.url}/redirect-to-request?jiraIssueIdOrKey={issueIdOrKey} |
Here, you need to enter the URL of Customer Case and the key or id of the appropriate issue.
For example:
https://stiltsoft.customercase.com/redirect-to-request?jiraIssueIdOrKey=CC-31
You will be redirected to the related request in Customer Case. You may be prompted to enter your username and password when accessing forums requiring authentication.
The token will be applied within 120 seconds.
Yes, it is possible. Learn about it in the following guidelines.
Yes, it is possible. Read the information on this page and contact us upon reading.