|
|
Field Option Sync |
Search Field (Panel) |
Search Field (Custom Field) |
Info Panel |
Info Panel (Custom Field) |
Dependant Field |
Asset Field |
|---|---|---|---|---|---|---|---|
|
Number of values |
up to 6k |
Fetch: up to 100k External: depends on data source |
Fetch: up to 100k External: depends on data source |
- |
- |
- |
up to 100k |
|
Field Type * |
NATIVE |
Virtual |
NATIVE |
Virtual |
NATIVE |
NATIVE |
NATIVE |
|
Is a Jira native field |
YES |
NO |
YES |
NO |
YES |
YES |
YES |
|
Writes to Jira native custom field |
YES |
YES |
YES |
NO |
YES |
YES |
YES |
|
Real-time |
NO |
YES |
YES |
YES |
YES |
NO |
YES |
|
Can use work item variable |
NO |
YES |
YES |
YES |
YES |
YES |
NO |
|
Can be dependant on other values (Context Filter) |
NO |
YES |
YES |
YES |
YES |
YES |
NO |
|
Company managed spaces |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Team managed spaces |
Restricted |
YES |
YES |
YES |
YES |
YES |
YES |
|
JSM Support |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
JSM Forms |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
|
Field Context |
YES |
Restricted |
YES |
NO |
YES |
YES |
YES |
|
Dashboard Usage |
YES |
Restricted |
NO |
NO |
NO |
YES |
NO |
|
Placement Options |
|
||||||
|
Work Item View |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Jira Create Work Item Screen |
YES |
NO |
YES |
NO |
YES |
NO |
YES |
|
JSM Create Request Screen |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
JSM Customer Portal |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Transition Screen |
YES |
NO |
YES 1 |
NO |
YES 1 |
NO |
YES 1 |
|
General |
|
||||||
|
Error Logs |
YES |
NO |
NO |
NO |
NO |
YES |
NO |
|
Error Notifications |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
1Only supported on the new transition experience.
Field Type: Virtual fields are a special type of field that are rendered in real-time and differ from NATIVE custom fields. Please note that even if a virtual field targets a native custom field, it does not inherit the behavior of the native custom field. As a result, adding the target field alone to screens will not produce the desired outcome. To ensure correct functionality, virtual fields must be explicitly placed in the field configuration.
Field Context: Restricted for the Search Field indicates that field contexts apply exclusively to the target field, not its virtual components.
Dashboard Usage: Restricted for the Search Field indicates that dashboard usage is limited to the target field value, excluding option selection typically found in native Jira select-lists.
Field Option Sync: Restricted indicates that you can not target a custom field of a team managed space directly, but you can now use global custom fields in team managed spaces.
