List of supported Custom Fields and Custom Field Types

List of supported Custom Fields and Custom Field Types

Select Lists include disabled options

Within Jira it is possible to disable individual values from selection lists. These values are then no longer offered in Jira. Since Jira version 8.12 (further details: https://jira.atlassian.com/browse/JRASERVER-60274) this information is also available in the Rest interface. 

Confluence administrators can enable the "Hide disabled select options"-function since version 3.1.3.

Jira Core standard Fields

Supported

Field Name

Note

Supported

Field Name

Note

Affects Version/s

since 1.1.0

Assignee

since 1.1.0

Attachment

since 2.2.0

Comment

Note within Jira: This field can not be placed on screens by users.

Component/s

since 1.1.0

Description

since 1.1.0

Due Date

since 1.1.0

Environment

since 1.1.0

Fix Version/s

since 1.1.0

Issue Type

Is part of the Issue Create form.

Labels

since 1.1.0

Linked Issues

Cannot be implemented without misbehaviour.

Priority

since 1.1.0

Reporter

since 1.1.0

Resolution

since 2.2.0 Supported by Issue Forms but ignored by Jira.

Status

Changing the status (using a transition) can open a screen to provide more details (e.g. the resolution) and the status change can be prevented by a validator. To change statuses you need to switch to Jira.

Security Level

since 1.2.0

Summary

since 1.1.0

Timetracking 

since 2.1.0

Jira Software standard Custom Fields

Supported

Field Name

Note

Field Type

Description within Jira

Supported

Field Name

Note

Field Type

Description within Jira

Business Value

since 1.1.0

Number Field

Measurement of business value of a requirement.

Date Custom Field

since 1.1.0

Date Picker

 

Epic Color 

Internal Jira Software usage only

Color of Epic

Epic Color field for Jira Software use only.

Epic Link

since 2.2.0

Epic Link Relationship

Choose an epic to assign this issue to.

Epic Name

since 1.1.0

Name of Epic

Provide a short name to identify this epic.

Epic Status

Internal Jira Software usage only

Status of Epic

Epic Status field for Jira Software use only.

Epic/Theme

since 1.1.0

Labels

Field that will help you regroup issues under an Epic or under a theme.

Flagged

since 1.1.0

Checkboxes

Allows to flag issues with impediments.

Rank

Internal Jira Software usage only

Global Rank

Global rank field for Jira Software use only.

Sprint

since 2.2.0

Jira Sprint Field

Jira Software sprint field.

Story Points

since 1.1.0

Number Field

Measurement of complexity and/or size of a requirement.

Jira Service Desk standard Custom Fields

Supported

Field Name

Note

Field Type

Description within Jira

Supported

Field Name

Note

Field Type

Description within Jira

Customer Request Type

https://aevolu.atlassian.net/browse/JINC-22

Customer Request Type Custom Field

Holds information about which Service Desk was used to create a ticket. This custom field is created programmatically and must not be modified.

Request participants

https://aevolu.atlassian.net/browse/JINC-22

Request Participants

 

Satisfaction

https://aevolu.atlassian.net/browse/JINC-22

Satisfaction

Stores request feedback in Service Desk requests. This custom field is created programmatically and required by Service Desk.

Satisfaction date

https://aevolu.atlassian.net/browse/JINC-22

Satisfaction date

Stores request feedback date in Service Desk requests. This custom field is created programmatically and required by Service Desk.

Time to first response

https://aevolu.atlassian.net/browse/JINC-22

SLA Custom Field Type

This custom field was created by Jira Service Desk.

Time to resolution

https://aevolu.atlassian.net/browse/JINC-22

SLA Custom Field Type

This custom field was created by Jira Service Desk.

Portfolio for Jira Custom Fields

 

Tested with:

 

Supported

Field Name

Note

Supported

Field Name

Note

Target Start Date

since 2.4.0: Can cause misbehaviour. See: https://jira.atlassian.com/browse/JPOSERVER-2358

Target End Date

since 2.4.0: Can cause misbehaviour. See: https://jira.atlassian.com/browse/JPOSERVER-2358

Original Story Points

since 2.4.0

Parent link

since 2.4.0: Uses an unpublished rest interface of Portfolio and can't used within automatically rendered form.
See: Troubleshooting - Why does the field 'Parent Link' require an issue type?

Team

since 2.4.0: Uses an unpublished rest interface of Portfolio and can't used within automatically rendered form.
See:  https://jira.atlassian.com/browse/JPOSERVER-2421

Standard Custom Field Types

Supported

Custom Field Type

Note

Supported

Custom Field Type

Note

Checkboxes

since 1.1.0

Date Picker

since 1.0.x

Date Time Picker

since 1.1.0

 

Global Rank (JIRA Software Field)

Support – not planned

Group Picker (mutiple groups)

since 1.1.0

Group Picker (single group)

since 1.0.x

Hidden Job Switch (programmatically set)

Support – not planned

Job Checkbox (checkbox to choose whether or not to create a Perforce job)

Support – not planned

Labels

since 1.1.0

Number Field

since 1.1.0

Project Picker (single project)

since 1.1.0

Radio Buttons

since 1.1.0

Select List (cascading)

since 1.1.0

Select List (multiple choices)

since 1.0.x

Select List (single choice)

since 1.0.x

Text Field (multi-line)

since 1.0.x

Text Field (read only)

Support – not planned

Text Field (single line)

since 1.0.x

URL Field

since 1.1.0

User Picker (multiple users)

since 1.1.0

User Picker (single user)

since 1.0.x

Version Picker (multiple versions)

since 1.0.x

Version Picker (single version)

since 1.1.0

Other Apps

App

Custom Field Type

Note

App

Custom Field Type

Note

JSU - Suite Utilities for Jira

  • Location text field

  • Location select field

  • Direction field

since 2.6.0 (tested with version 2.7.0 of JSU - Suite Utilities for Jira)

Project Specific Select Field

  • Project Specific Select Field

  • Project Specific Multi Select Field

since 2.6.0 (tested with version 2.6.1 of Project Specific Select Field)

Checklist for Jira

  • Checklist Field

since 2.7.0 (tested with version 4.0.3 of Checklist for Jira)
default options (defined in Jira) can be used within Issue Forms

since 2.7.1 (tested with version 4.0.3 of Checklist for Jira)
add new items within Issue Forms (requires Confluence >= 5.10)