Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

This function filters an issue list using the given comparison for number fields.

Syntax
filterByFieldValue(issueList, numberField, operator, number) #Output: Issue list
Examples
Parser expressionDescription
filterByFieldValue(issuesUnderEpic(), {issue.cf10110}, >, 10)

This example returns an issue list with all issues under the current epic that have more than 10 story points assigned to them.

Note that {issue.cf10110} is in this example the field code for the field "Story Points".

To achieve this, the following functions are used:

filterByFieldValue(subtasks(), {issue.dueDate}, =, null)

This example returns an issue list with all sub-tasks that don't have a due date set.

To achieve this, the following functions are used:

Additional information

Parameters used in this function

ParameterInput (data type)Description
issueList

ISSUE LIST

Any given issue list. Usually this value is retrieved from a function (e.g. linkedIssues() or subtasks()).
numberField

TEXT

Any field code representing a number field or a selectable field.
operator

OPERATOR

One of the following comparison operators: =, !=, <, <=, > and >=.
number

NUMBER

Any given number or null that will be used in combination with the operator to filter the given list.
Output

This function returns an ISSUE LIST.

If the issue list is empty or the comparison won't be fullfilled by any issue, the function returns an empty ISSUE LIST.


Variant for text fields.

Syntax
filterByFieldValue(issueList, textField, operator, text) #Output: Issue list
Examples
Parser expressionDescription
filterByFieldValue(linkedIssues(), %{issue.component}, ~, "Web")

This example returns an issue list with linked issues where the component "Web" is set.

To achieve this, the following functions are used:

filterByFieldValue(subtasks(), %{issue.status}, in, "Done, Closed, Canceled")

This example returns an issue list with all sub-tasks that are in one of the specified status: Done, Closed or Canceled.

To achieve this, the following functions are used:

filterByFieldValue(siblingSubtasks(), %{issue.summary}, ~, %{issue.summary})

This example returns an issue list with all sibling sub-tasks that have the same summary like the current issue.

To achieve this, the following functions are used:


filterByFieldValue(subtasks(), %{issue.description}, ~, null)

This example returns an issue list with all sub-tasks of the current issue that don't have a description.

To achieve this, the following functions are used:

Additional information

Parameters used in this function

ParameterInput (data type)Description
issueList

ISSUE LIST

Any given issue list. Usually this value is retrieved from a function (e.g. linkedIssues() or subtasks()).
textField

TEXT

Any field code representing a text field or a selectable field.
operator

OPERATOR

One of the allowed comparison operators.
text

TEXT

Any given text or null that will be used in combination with the operator to filter the text list.

Can also contain a comma separated list with strings.

Output

This function returns an ISSUE LIST.

If the issue list is empty or the comparison won't be fullfilled by any issue, the function returns an empty ISSUE LIST.

If you want to filter by a more complex boolean expression, use the function filterByPredicate().

If you prefer using a JQL query to filter your results you can use issuesFromJQL()


Use cases and examples

Use case
No content found.