JWT calculated fields

JWT ships with three custom field types to calculate field values, display live data, or even pull data from online service providers such as Google.

Each custom field type, from number to text, or date-time fields, comes with a different set of options that let you define exactly what you want to see as a result using the full power of the JWT expression editor.

Last but not least, you can individually define how the result of the calculation should appear, from different time formats to currency symbols, by configuring individual Display formats.

Interested in configuring calculated fields? Find detailed information here.

Field types

🗓️ Calculated date-time fields

This type of read-only custom field contains a value which is dynamically calculated from a custom math/time expression. It can be used to obtain a date-time value depending on the value of the current issue or in other issues.

🔢 Calculated number fields:

This type of read-only custom field has a value which is dynamically calculated from a custom math/numeric expression. It can be used to obtain a numeric value depending on the value of other fields in the current issue or in any other issues.

🔤 Calculated text fields

This type of read-only custom field has a value which is dynamically calculated from a custom text expression. It can be used to show a text composed from one or more field values returned by field codes.

📚 Calculated fields library

• Date-time fields

• Number fields

Use case Field type JWT feature Label Parser functions
Number of unresolved blocking issues

Number

(blue-star) 

staff pick

count()

filterByResolution()

linkedIssues()

Number of times a custom field has been changed

Number

(blue-star) 


count()

fieldChangeTimes()

Sum of field value from issues in JQL query

Number

(blue-star) 


sum()

fieldValue()

issuesFromJQL()

Total remaining estimate in an epic (no sub-tasks)

Number

(blue-star) 


sum()

fieldValue()

issuesUnderEpic()

Total time logged on an epic

Number

(blue-star) 


sum()

fieldValue()

issuesUnderEpic()

Difference between the current date and the earliest due date

Number

(blue-star) 


min()

fieldValue()

subtasks()

Total remaining estimate in an epic (all linked issues)

Number

(blue-star) 


sum()

fieldValue()

issuesUnderEpic()

subtasks()

Number of issues in the same version

Number

(blue-star) 


count()

issuesFromJQL()

Months elapsed

Number

(blue-star) 


month()

Time left before the issue is due

Number

(blue-star) 


max()

Sum of Tempo billable hours

Number

(blue-star) 


executeRemoteAction()

toNumberList()

sum()

toNumber()

Number of times a resolved issue has been rejected

Number

(blue-star) 


count()

timesOfTransition()

Number of hours in the current priority

Number

(blue-star) 


timeInValue()

Number of open subtasks

Number

(blue-star) 


count()

filterByPredicate()

subtasks()

Total of all story points in an epic

Number

(blue-star) 

staff pick

sum()

fieldValue()

issuesUnderEpic()

Number of days an issue was in the Open status against a JWT calendar

Number

(blue-star) 


timeInStatus()

Operate with field values from sub-tasks

Number

(blue-star) 


Elapsed time between creation and resolution

Number

(blue-star) 

staff pick

Highest value out of several fields

Text

(blue-star) 


max()

• Text fields