fieldValue()

This function returns a number list with values of a given field from the given issues.

Syntax

fieldValue(numberField, issueList) #Output: Number list

Parser expression

Description

fieldValue({issue.dueDate}, subtasks())

This example returns a number list of the sub-tasks' Due Dates.

To achieve this, the following functions are used:

subtasks()

sum(fieldValue({issue.cf10203}, subtasks()))

This example returns the sum of all story point estimates (with the custom field ID 10203) of all subtasks.

To achieve this, the following functions are used:

Parameters used in this function

Parameter	Input (data type)	Description
`numberField`	TEXT	Any field code representing a number field or a selectable field.
`issueList`	ISSUE LIST	Any given issue list. Usually this value is retrieved from a function (e.g. linkedIssues() or subtasks()).

This function returns a NUMBER LIST.

If the issue list is empty or there are no values for the field in the given issue list, the function returns an empty NUMBER LIST.

Variant for text fields.

Syntax

fieldValue(textField, issueList) #Output: Text list

Parser expression	Description
fieldValue(%{issue.reporter}, subtasks())	This example returns the text list of the sub-tasks' reporters. To achieve this, the following functions are used: subtasks()

Parameters used in this function

Parameter	Input (data type)	Description
`textField`	TEXT	Any field code representing a text field or a selectable field.
`issueList`	ISSUE LIST	Any given issue list. Usually this value is retrieved from a function (e.g. linkedIssues() or subtasks()).

This function returns a TEXT LIST.

If the issue list is empty or there are no values for the field in the given issue list, the function returns an empty TEXT LIST.

This function always returns a list, even when only a single issue is read. The easiest way to return this single value then, is the usage of first().

Use cases and examples

Use case	Workflow function	Field type	Automated action	Parser functions
Sum of field value from issues in JQL query		Number		sum() fieldValue() issuesFromJQL()
Difference between the current date and the earliest due date		Number		min() fieldValue() subtasks()
Inherit value from parent in Advanced Roadmaps hierarchy			Update field action	fieldValue() first() parent()
Add components of the epic to the current issue			Update field action
Link to the linked epic from the current issue		Text		toString() fieldValue() issueKeysToIssueList()
Sum up value in parent issue on field change in sub-tasks			Update field action	fieldValue() sum() subtasks()
Clone epic, tasks and sub-tasks	Create issue			toString() toStringList() issueKeysToIssueList() replaceFirst() first() fieldValue() textOnStringList() findModify() subtasks() issuesUnderEpic()
Total time logged on an epic		Number		sum() fieldValue() issuesUnderEpic()
Total remaining estimate in an epic (no sub-tasks)		Number		sum() fieldValue() issuesUnderEpic()
Highest ranked custom field value among all linked issues		Text		first() sort() fieldValue() linkedIssues()
Components from all sub-tasks		Text		toString() distinct() fieldValue() subtasks()
Total remaining estimate in an epic (all linked issues)		Number		sum() fieldValue() issuesUnderEpic() subtasks()
Total of all story points in an epic		Number		sum() fieldValue() issuesUnderEpic()
Creation date of the linked epic		Date-time		first() fieldValue() linkedIssues()
Set Due Date with latest value among sub-tasks	Update or copy field values			fieldValue() max() siblingSubtasks()
Ensure that all issues linked with a certain issue link type have "Due Date" field set	Logical validator Logical condition			count() linkedIssues() fieldValue()

Content

Space Tools

Use cases and examples