Info | ||
---|---|---|
| ||
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 | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
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 |
...
Supported | Field Name | Note | Field Type | Description within Jira | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Customer Request Type |
| 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 |
| Request Participants | ||||||||||
Satisfaction |
| Satisfaction | Stores request feedback in Service Desk requests. This custom field is created programmatically and required by Service Desk. | |||||||||
Satisfaction date |
| 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 |
| SLA Custom Field Type | This custom field was created by Jira Service Desk. | |||||||||
Time to resolution |
| SLA Custom Field Type | This custom field was created by Jira Service Desk. |
Portfolio for Jira Custom Fields
...
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 |
...
App | Custom Field Type | Note |
---|---|---|
JSU - Suite Utilities for Jira |
| since 2.6.0 (tested with version 2.7.0 of JSU - Suite Utilities for Jira) |
Project Specific Select Field |
| since 2.6.0 (tested with version 2.6.1 of Project Specific Select Field) |
Checklist for Jira |
| since 2.7.0 (tested with version 4.0.3 of Checklist for Jira) since 2.7.1 (tested with version 4.0.3 of Checklist for Jira) |