How to create new calculated custom field?
You can find all new fields by: JBCF |
There are many dynamic fields in this pack. Their values fall into the search index when indexing tasks. It is enough to add any of the fields 1 time per instance.
Field for maintaining lists with the ability to mark completed items.
Description: The list of projects is set in the field settings. In this field you can select components from the specified projects
Value: Components
Search: The field stores the value in the index.
Description: The list of statuses(issue status) is set in the field settings. One of these statuses is selected as the field value.
Value: Status
Search: The field stores the value in the index.
Description: This field shows the previous status of the task.
Value: Status
Search: The field stores the value in the index.
Description: The list of Project Roles is set in the field settings. One of these roles is selected as the field value.
Value: Project role
Search: The field stores the value in the index.
Description: The list of groups is set in the field settings. One of these groups is selected as the field value.
Value: Group
Search: The field stores the value in the index
Can use in permission and notification schemes
This field allows you to calculate intersections, merges, and differences between two fields containing versions.
Field for counting the number of specified type of links for issue or number of links for issues in specified statuses.
Converts the date-time from the selected field (server time zone) to the date-time of the specified time zone.
Convert Date-time to the specified TimeZone
Show all users from comments. By mentions(this field) you can search(JQL)
Value: Users
Search: The field stores the value in the index.
Can use in permission and notification schemes
Description: Elapsed time from the moment the task was created to the current time. You can choose the time output format and connect the work calendar. (see Time between dates )
Value: Number - time in seconds
Search: The field stores the value in the index. (see https://jibrok.atlassian.net/wiki/spaces/JBS/pages/694255617/Time+between+dates#JQL-functions )
Description: The elapsed time from the moment the task was created to the resolution. You can choose the time output format and connect the work calendar. (see Time between dates )
Value: Number - time in seconds
Search: The field stores the value in the index. (see https://jibrok.atlassian.net/wiki/spaces/JBS/pages/694255617/Time+between+dates#JQL-functions )
Type: Number
Search: The field stores the value in the index.
Description: List of links to issue attachments
Value: null - The field only displays the links. Sort attachment by file type.
Search: The field does not store the value in the index.
Value: Number
Search: The field stores the value in the index.
Description: Shows the last comment available to the current user.
Value: null - The field only displays the last comment.
Search: The field does not store the value in the index.
Description: Previous assignee by issue history.
Value: User
Search: The field stores the value in the index.
Can use in permission and notification schemes
Description: Show users who were assignee
Value: Users
Search: The field stores the value in the index.
Can use in permission and notification schemes
Description: The user who last posted the resolution in issue.
Value: User
Search: The field stores the value in the index.
Can use in permission and notification schemes
Value: Number
Search: The field stores the value in the index.
Description: Get list of subtasks without resolution.
Value: String - list of subtask keys
Search: The field stores the value in the index.
Description: Get list of subtasks with resolution.
Value: String - list of subtask keys
Search: The field stores the value in the index.
Value: Status
Search: The field stores the value in the index.
Description: Field for sorting tasks by parent task. In the search results, when sorting by this field, all subtask will follow their parental task.
Value: The field returns the key of the parent task. On issue screens, adding a field is optional.
Search: The field stores the value in the index.
Description: Field for sorting tasks by parent task. In the search results, when sorting by this field, all subtask will follow their parental task.
Value: The field returns the key of the parent task. On issue screens, adding a field is optional.
Search: The field stores the value in the index.
Description: Field for sorting tasks according to the epic specified in the task. When sorting by this field, the tasks in the search results will be after the epic specified in the task.
Value: String: The field returns the key of the task. On issue screens, adding a field is optional.
Search: The field stores the value in the index.
Description: The field for sorting tasks by the rank specified in the epic task. When sorting by this field, the tasks in the search results will be after the epic specified in the task. All epics will be sorted by their rank. All tasks from the epic will be under the epic. All tasks under the epic will be sorted by their rank.
Value: String: The field returns the key of the task. On issue screens, adding a field is optional.
Search: The field stores the value in the index.
Description: The date of the first comment that is available to the current user.
Value: Date and time
Search: The field stores the value in the index.
Description: The date of the last comment that is available to the current user.
Value: Date and time
Search: The field stores the value in the index.
Description: In the field settings, select the status. This field shows the date and time when the issue last changed to this status.
Value: Date and time
Search: The field stores the value in the index.
Description: The author of the last comment that is available to the current user.
Value: User
Search: The field stores the value in the index.
Can use in permission and notification schemes
Description: List of leads specified in the issue components.
Value: Users
Search: The field stores the value in the index.
Can use in permission and notification schemes
Description: Project lead for current issue
Value: User
Search: The field stores the value in the index.
Can use in permission and notification schemes
Description: Show assignee, reporter and all comments that is available to the current user
Value: Html
Search: no search
Description: Show assignee, reporter and last comment that is available to the current user
Value: Html
Search: no search
Description: Show list inward issues
Value: Issues
Search: no search
Description: Show list outward issues
Value: Issues
Search: no search
Description: Show list inward issues group by link type. Include epic links.
Value: Html
Search: no search
Description: Show list outward issues group by link type. Include epic links.
Value: Html
Search: no search
Description: Show list inward issues group by link type. Include sub-task/parent and epic links.
Value: Html
Search: no search
Description: Show list outward issues group by link type. Include sub-task/parent and epic links.
Value: Html
Search: no search
Description: Show all linked issues group by link type. Include sub-task/parent and epic links.
Value: Html
Search: no search
Description: This field checks the input string for matching a regular expression. Can check each line separately.
Value: String
Search: The field stores the value in the index.
Description: ield for search and display remote links
Value: String
Search: The field stores the value in the index.
Description: Time range selection field
Value: String
Search: no search
Description: Select one file from the list attached to the issue
Value: Attachment
Search: no search
Description: Select one or more files from the list attached to the issue
Value: List of Attachments
Search: no search
Description: Counts the number of changes to the field specified in the settings. For example, that the "sprint" field was changed 10 times.
Value: Number
Search: The field stores the value in the index.