Supported fields
If you need or use a particular field that is not supported, or have any questions, please contact the Nemetschek Bulgaria Support Team.
Supported fields
Standard System and Custom Fields
All standard Jira fields are supported (key, summary, description, dates, texts, lists, etc.).
Details about some of the supported fields:
Linked issues
As a JSM project administrator, you can allow Linked issues to be visible for your portal customers. This will show them the keys of all linked issues that exist in Jira for the request (incl. links to software projects), even the ones they do not have access to. However, no one can open a request they don’t have access to and we don’t show the summary or any other sensitive information.
Asset fields
As a JSM project administrator, you can allow the label of fields of type Asset to be visible in the report on the portal for JSM Help Center customer by adding the fields from the project configuration. You can select the label of which field of type Asset to be shown by adding it from the select menu and then save the configuration.
Filtering by Insight Objects: Data Center / Server
If you use Insight fields in a way that we currently do not support, please contact us to discuss how to accommodate your use case.
Attachments
As a JSM project administrator, you can allow fields of type Attachment to be visible and available to download on the portal for JSM Help Center customer by adding the fields from the project configuration.
If the JSM project administrator allows a field of type Attachment to be visible on the portal, the JSM Help Center customer will be able to see and download the attachment (in file format, such as: pdf., png., jpg.).
Unsupported fields
Third-party fields (incl. ProForma and Tempo)
Third-party app fields are currently unsupported due to Atlassian APIs. Examples of such unsupported fields are Elements Connect, ProForma, Tempo, Custom Field Suite, etc.