...
Custom Field | Description | Examples of usage | ||
|---|---|---|---|---|
Completed Story Points | Sums the story points for closed Issues under the Epic. The field is available for Epic issue Issue type. |
| ||
Completed Issues By Percentage | The percent of closed Issues under an Epic. The field is available for Epic issue Issue type.
| |||
Modified By | The user that made the last update to the Issue.
|
| ||
Number Of Stories | Number of Stories assigned to the Epic. The field is available for Epic issue Issue type and calculates only Story issue Issue type under the Epic. |
| ||
Parent Status | The status of a Sub-tasks Parent Issue. The field is available for Sub-task issue Issue type. |
| ||
Parent Field Value | The value of a custom field from the Parent Issue. The field is available for Sub-task issue Issue type. You have to specify the custom field ID of the Parent field on the Configuration page. |
| ||
Previous Assignee | The previous user who was assigned to an Issue. |
| ||
Sum Of Story Points | Sums the story points for all Issues under the Epic. The field is available for Epic issue Issue type. |
| ||
Time in Previous Status | Amount of time that the custom field has been in the previous status.
|
| ||
Un-sized Issues | The number of Issues in the Epic that do not have an estimate. The field is available for Epic issue Issue type. |
|
Power Custom Fields in
...
an Issue
You are able to configure the issue Issue layout changing the position and visibility of fields in the issue Issue view. Power Custom Fields can be shown viewed in the Description fields and Contexts fields sections of the ticket.
| Note |
|---|
Power Custom Fields are updated as soon as we detect changed data data changes within a particular issue Issue or linked issues to itIssues. Unfortunately, due to Jira cloud limitations, it may take several seconds. To enable the field calculation for previously created tickets, an issue Issue update can be required. |
Usage of Power Custom Fields
Power Custom Fields are searchable and you can use them for JQL, better view and export issues Issues statistics.
