Dynamic Custom Field Templates
Dynamic Custom Fields offers over 50 pre-configured templates that can be used as custom fields in your work items.
Template Name | Description |
|---|---|
Assignee user groups | All user groups in which the work item's assignee is a member |
Attachment authors | All users that have added attachments to the work item |
Attachment filenames | All filenames of the work item's attachments |
Attachment file types | All file types of the work item's attachments (e.g. image/png) |
Attachment total size | The total size of the work item's attachments |
Completed child work item percentage | The percentage of completed child work item of the work item (subtasks or Stories of an Epic) |
Comment authors | All users that have commented on the work item |
Days in previous status | The number of days the work item was in the previous status |
First assignee | The first assignee of the work item |
First attachment date | The date the first attachment was added to the work item |
First comment | The first comment of the work item |
First commenter name | The name of the first commenter of the work item |
First comment date | The date of the first comment of the work item |
First subtask created date | The created date of the oldest subtask under the work item |
Work item ID (internal) | The work item ID is an immutable ID within Jira, which won’t change even if you move the work item between spaces. The work item ID has at least 5 digits, for example 12345. |
Work type description | The description of the work type |
Last assignee change author | The user who last changed the work item's assignee |
Last assignee change date | The date the work item's assignee was last changed |
Last comment | The last comment of the work item |
Last commenter name | The name of the last commenter of the work item |
Last comment date | The date of the last comment of the work item |
Last work item update author | The user that made the last update to the work item |
Last status change author | The user who last changed the work item status |
Last status change date | The date on which the work item status was last changed |
Last subtask created date | The created date of the newest subtask under the work item |
Number of affected versions | The number of affected versions in the work item |
Number of assignee changes | The number of times the work item's assignee was changed |
Number of attachments | The number of attachments in the work item |
Number of attachment authors | The number of users that have added attachments to the work item |
Number of child work items | The number of child work items in the work item (subtasks or Stories of an Epic) |
Number of child attachments | The number of attachments of all child work items (e.g. subtasks) |
Number of child comments | The number of comments of all child work items (e.g. subtasks) |
Number of comments | The number of comments in the work item |
Number of comment authors | The numbers of users that have commented on the work item |
Number of components | The number of components in the work item |
Number of fix versions | The number of fix versions in the work item |
Number of work item links | The number of work item links in the work item |
Number of work item links of a specific type | The number of work item links of a specific type (as default value the type “Blocks” is selected) |
Number of labels | The number of labels in the work item |
Number of status changes | The sum of all status changes of an work item |
Number of stories | Number of stories linked to the Epic - empty if the work item is not an Epic |
Number of subtasks | The number of subtasks under a parent work item |
Number of subtask attachments | The sum of all attachments of all subtasks |
Number of subtask comments | The number of comments of all subtasks which are under a parent work item (e.g. story) |
Parent assignee | The assignee of the parent work item (This field can be used in work item hierarchies. For example, if a subtask is the child work item of a story, you can display the assignee of the parent story within the subtask.) |
Parent created date | The created date of the parent work item (This field can be used in work item hierarchies. For example, if a subtask is the child work item of a story, you can display the created date of the parent story within the subtask.) |
Parent field value | The value of a custom field from the parent work item |
Parent work item key | The work item key of the parent work item (This field can be used in work item hierarchies. For example, if a subtask is the child work item of a story, you can display the work item key of the parent story within the subtask.) |
Parent work type | The work type of the parent work item (This field can be used in work item hierarchies. For example, if a subtask is the child work item of a story, you can display the work type of the parent story within the subtask.) |
Parent priority | The priority of the parent work item (This field can be used in work item hierarchies. For example, if a subtask is the child work item of a story, you can display the priority of the parent story within the subtask.) |
Parent Space | The space key of the parent work item (This field can be used in work item hierarchies. For example, if a subtask is the child work item of a story, you can display the space name of the parent story within the subtask.) |
Parent reporter | The reporter of the parent work item (This field can be used in work item hierarchies. For example, if a subtask is the child work item of a story, you can display the reporter of the parent story within the subtask.) |
Parent resolution | The resolution of the parent work item (This field can be used in work item hierarchies. For example, if a subtask is the child work item of a story, you can display the resolution of the parent story within the subtask.) |
Parent resolution date | The resolution date of the parent work item (This field can be used in work item hierarchies. For example, if a subtask is the child work item of a story, you can display the resolution date of the parent story within the subtask.) |
Parent status | The status of the parent work item (This field can be used in work item hierarchies. For example, if a subtask is the child work item of a story, you can display the status of the parent story within the subtask.) |
Parent updated date | The last updated date of the parent work item (This field can be used in work item hierarchies. For example, if a subtask is the child work item of a story, you can display the updated date of the parent story within the subtask.) |
Previous assignee | The previous user who was assigned to the work item |
Priority description | The description of the work item’s priority |
Space key | The work item’s space key |
Space type (software/business/service_desk) | The type of the space in which the work item is located (“service_desk” refers to a service management space.) |
Space style (classic/next-gen) | The style of the space in which the work item is located (“classic” refers to a company-managed space (project), “next-gen” refers to a team-managed space (project)) |
Reporter user groups | All user groups in which the work item reporter is a member |
Status description | The description of the work item status |
Subtask affected versions | The affected versions of all subtasks under the work item |
Subtask assignees | The assignees of all subtasks under the work item |
Subtask components | The components of all subtasks under the work item |
Subtask fix versions | The fix versions of all subtasks under the work item |
Subtask keys | The keys of all subtasks under the work item |
Subtask labels | The labels of all subtasks under the work item |
Subtask priorities | The priorities of all subtasks under the work item |
Subtask reporters | The reporters of all subtasks under the work item |
Subtask statuses | The statuses of all subtasks under the work item |
