Wiki

Clone wiki

calculated-custom-fields / Home

Calculated custom fields

How create new calculated custom field?

Adding a custom field

You can find all new fields by: JBCF create fields.png

1. All fields are dynamic. Their values ​​fall into the search index when indexing tasks.

2. It is enough to add any of the fields 1 time per instance.

Age

  • Description: Elapsed time from the moment the task was created to the current time.
  • Value: Number - time in seconds
  • Search: The field stores the value in the index.

Age by resolution

  • Description: The elapsed time from the moment the task was created to the resolution.
  • Value: Number - time in seconds
  • Search: The field stores the value in the index.

Count of attachment

  • 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.
  • Search: The field does not store the value in the index.

Count of comment

  • Value: Number
  • Search: The field stores the value in the index.

Last comment

  • 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.

Resolver

  • Description: The user who last posted the resolution in issue.
  • Value: User
  • Search: The field stores the value in the index.

Not resolves sub-tasks

  • Description: Get list of subtasks without resolution.
  • Value: String - list of subtask keys
  • Search: The field stores the value in the index.

Resolves sub-tasks

  • Description: Get list of subtasks with resolution.
  • Value: String - list of subtask keys
  • Search: The field stores the value in the index.

Parent status

  • Value: String - Parent task status name
  • Search: The field stores the value in the index.

Sort by parent ASK

  • 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.

Sort by parent DESC

  • 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.

Sort by epic

  • 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.

Sort by epic rank

  • 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.

Updated