---
title: "User guide"
canonical: "https://support.appfire.com/space/PC/14286852/User%20guide"
format: markdown
---
> Macro (aura-html)
Calculated Power Custom Fields improve the user experience and allow you to customize Jira to better suit your needs.
### Available Power Custom Fields in Jira cloud
| **Custom Field** | **Description** | **Examples of usage** |
| --- | --- | --- |
| #### Completed Story Points | Sums the story points for closed Issues (Works) under the Epic.
To determine if a Work is closed, we use the Status Category "Done".
The field will only work for the Epic Issue type (Work type) (hierarchy level 1).
If the "Story Points" is empty, the "Story point estimate" field will be used instead. |  |
| #### Completed Issues By Percentage | The percent of closed Issues (Works) under an Epic.
To determine if a Work is closed, we use the Status Category "Done".
The field will only work for the Epic Issue type (hierarchy level 1).
> ℹ️ Note that sub-tasks are not taken into account. |
| #### Modified By | The user that made the last update to the Issue. |  |
| #### Number Of Stories | Number of Stories assigned to the Epic.
The field will only work for the Epic Issue type (hierarchy level 1), and calculates only Story Issue type (work type) under the Epic (hierarchy level 0).
We're using either the "Epic Link" and if not found, we're using the "Parent" field in the children Stories. |  |
| #### Parent Status | The status of a Sub-task's Parent Issue (Work).
The field will only work for Sub-task Issue (Work) type. |  |
| #### Parent Field Value | The value of a custom field from the Parent Issue.
The field will only work for the Sub-task Issue (Work) type. You have to specify the custom field ID of the Parent field on the [Configuration page](https://anovaapps.atlassian.net/wiki/spaces/PCFC/pages/548929591/Configuring+Power+Custom+Fields). |  |
| #### Previous Assignee | The previous user who was assigned to an Issue (Work). |  |
| #### Sum Of Story Points | Sums the story points for all Issues (Works) under the Epic.
The field will only work for the Epic Issue type (Work type) (hierarchy level 1).
If the "Story Points" is empty, the "Story point estimate" field will be used instead. |  |
| #### Time in Previous Status | Amount of time that the custom field has been in the previous status.
> ℹ️ Note that the field does not appear on the screen until the status of the Issue changes. |  |
| #### Un-sized Issues | The number of Issues (Works) under an Epic that have an empty "Original estimate" field.
The field will only work for the Epic Issue type (Work type) (hierarchy level 1). |  |
### Power Custom Fields in an Issue
You are able to configure the [Issue layout](https://support.atlassian.com/jira-software-cloud/docs/configure-field-layout-in-the-issue-view/) changing the position and visibility of fields in the Issue view. Power Custom Fields can be viewed in the Description fields and Contexts fields sections of the ticket.
> ⚠️ Power Custom Fields are updated as soon as we detect data changes within a particular Issue or linked Issues. Unfortunately, due to Jira cloud limitations, it may take several seconds.
> ⚠️
> ⚠️ To enable the field calculation for previously created tickets, an 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 statistics.
# What's next?
[FAQ](https://anovaapps.atlassian.net/wiki/spaces/PCFC/pages/222429287/FAQ)