Skip to main content

fieldValue

Overview​

The fieldValue function enables you to extract and compare values from specific fields in issues that match a given query. This is useful for comparing field values across issues or between different fields.

Syntax​

field operator fieldValue("subquery", "field_name")

Parameters​

  • subquery (required): A valid JQL query that defines the set of issues to extract values from
  • field_name (required): The name of the field to retrieve values from

Supported Operators​

  • =, != - exact matching
  • >, >=, <, <= - numerical/date comparisons
  • in, not in - list comparisons

Examples​

Comparing Story Points to estimate​

"Story Points" > fieldValue("project = DEV", "estimate")

Finds issues where Story Points is higher than the estimate value.

Finding issues where reporter equals assignee​

reporter = fieldValue("project = DEV", "assignee")

Finding issues where fix version matches affected version​

fixVersion in fieldValue("project = DEV", "affectedVersion")

Finding issues resolved after due date​

resolutionDate > fieldValue("project = DEV", "dueDate")

Supported Field Types​

The fieldValue function works with:

  • Text fields (Summary, Description)
  • Number fields
  • Date fields
  • User fields
  • Label fields
  • Version and Component fields
  • Custom fields of the above types

For custom fields, use the field's display name (e.g., "Story Points" instead of "customfield_10001").

Performance Considerations​

  • Text field comparisons are generally faster than complex field types
  • Date and number comparisons may require additional processing
  • User and label field comparisons may involve additional lookups
  • Large subqueries may impact performance; use specific filters when possible

Error Handling​

The function will return an error if:

  • The specified field name is not valid or not found
  • The JQL subquery is invalid
  • The operator is not compatible with the field type