Frequently Asked Questions (FAQ)
How do I configure translated custom fields for a request type on the Jira Service Management portal?
Currently the process of adding fields to a request type differs from the standard Jira flow. This is due to limitations in how Jira Service Management supports third-party fields on the customer portal. We’ve documented the custom process in detail in Translated form configuration
Since standard Jira features still don’t fully support third-party fields on the portal, our app provides an additional panel at the bottom of the request form. This panel displays the fields added via the configuration available under 'Translated form' in the JSM project settings.
To display Translated Fields on the portal:
Navigate to ⚙️ Project settings in your Jira Service Management project.
Open the new section called Translated form.
Click on the request type where you want to add Translated fields. You can enable the form extension now or after you finish configuring the form.
On the right side, all available Translated fields will be listed.
Click on a field to add it to the form.
Use drag and drop to rearrange the fields as needed.
Click Save to apply your changes.
Congratulations! The request form with Translated fields is now visible on the Customer Portal.
Recently, Atlassian introduced partial support for custom fields from Forge apps, which now allows them to be added to the standard request type configuration. However, these fields are not rendered correctly yet.
There’s an open ticket for this issue: FRGE-778 – Atlassian Ecosystem
We hope this limitation will be resolved soon, allowing for full integration of custom fields within the native portal UI.
Last updated