Sum of field value from issues in JQL query

Use case

This use case is appropriate for summing a field value of issues included in a JQL query.

Create a new Calculated Number Field (by JWT) custom field and name it properly.

Providing a description will help you to identify what the custom field does but this step is optional

Add the following expression:

sum(fieldValue({issue.cfAAAAA},issuesFromJQL("project = DEMO and fieldName is not empty")))

Add the field to the relevant view screens.

Remember: All calculated fields are read-only and cannot be manually updated on a create or edit screen.

Use case	Parser functions	Label
Difference between the current date and the earliest due date	min() fieldValue() subtasks()
Elapsed time between creation and resolution		STAFF PICK
Highest value out of several fields	max()
Months elapsed	month()
Number of days an issue was in the Open status against a JWT calendar	timeInStatus()
Number of hours in the current priority	timeInValue()
Number of issues in the same version	count() issuesFromJQL()
Number of open subtasks	count() filterByPredicate() subtasks()
Number of times a custom field has been changed	count() fieldChangeTimes()
Number of times a resolved issue has been rejected	count() timesOfTransition()
Number of unresolved blocking issues	count() filterByResolution() linkedIssues()	STAFF PICK
Operate with field values from sub-tasks
Sum of field value from issues in JQL query	sum() fieldValue() issuesFromJQL()
Sum of Tempo billable hours	executeRemoteAction() toNumberList() sum() toNumber()
Time left before the issue is due	max()
Total of all story points in an epic	sum() fieldValue() issuesUnderEpic()	STAFF PICK
Total remaining estimate in an epic (all linked issues)	sum() fieldValue() issuesUnderEpic() subtasks()
Total remaining estimate in an epic (no sub-tasks)	sum() fieldValue() issuesUnderEpic()
Total time logged on an epic	sum() fieldValue() issuesUnderEpic()

If you still have questions, feel free to refer to our support team.