/
Jira Service Management portal
Jira Service Management portal
Custom fields added to a request type in JSM will automatically hide and cannot be made visible, making it impossible to provide custom field types for JSM.
Jira Server / Data Center:
In Server / Data Center instances, it’s possible to add a custom field in the selected request type and hide it (giving a preset value that will be shown once the issue is created) or show it (so that the client can choose a selection).
Jira Cloud:
In a Cloud instance, however, there is no option to make any custom field visible to the client. This means that the custom field can only contain preset values selected in advance by the portal administrator.
With common fields, you get the option to hide the field. Click on it to give a preset value and hide the field.
Cloud custom fields do not have the checkbox, and the field remains hidden.
For reference, this is an Atlassian ticket on this matter: https://ecosystem.atlassian.net/browse/FRGE-778 .
, multiple selections available,
Related content
Migrate MLCS values of Jira issues (Cloud)
Migrate MLCS values of Jira issues (Cloud)
Read with this
CSV options import (Server / Data Center)
CSV options import (Server / Data Center)
Read with this
CSV issue import (Data Center)
CSV issue import (Data Center)
Read with this
MLCS Custom Field Configuration
MLCS Custom Field Configuration
Read with this
Multi-Level Cascading Select
Multi-Level Cascading Select
Read with this
Issue search by custom fields difference
Issue search by custom fields difference
Read with this