The following page contains use cases for the JWT calculated fields. The number of use cases will grow over time, so make sure to visit this page once in a while.
📅 Calculated date-time fields
| Use case | JWT feature | Field type | Parser functions | Label |
|---|---|---|---|---|
| Creation date of the linked epic |
|
STAFF PICK |
||
| Predicted completion date of an epic |
|
Date-time | addTimeSkippingWeekends() |
STAFF PICK |
| Predicted resolution date based on business hours |
|
addTime() |
|
|
| Set the calculated field's visibility in function of the username, role or group |
|
|
🔢 Calculated number fields
(input latin letters) Calculated text fields
| Use case | JWT feature | Field type | Parser functions | Label |
|---|---|---|---|---|
| Check if an issue was resolved on time |
(input latin letters) |
Text | datePart() |
|
| Components from all sub-tasks |
(input latin letters) |
|
||
| Details of the last comment |
(input latin letters) |
Text |
STAFF PICK |
|
| Difference between two dates in business days |
(input latin letters) |
Text | formatWorkDuration() timeDifference() |
|
| Display additional details of the issue creator |
(input latin letters) |
|
||
| Display current issue's project category |
(input latin letters) |
|
||
| Display historic due dates |
(input latin letters) |
|
||
| Display reporters of linked Cloud issues |
(input latin letters) |
Text |
|
|
| Google Maps location |
(input latin letters) |
Text |
STAFF PICK |
|
| Highest ranked custom field value among all linked issues |
(input latin letters) |
Text |
|
|
| Last comment, its author, and timestamp |
(input latin letters) |
Text |
STAFF PICK |
|
| Last commenter's full name |
(input latin letters) |
Text | userFullName() |
|
| Status and assignee of parent issue |
(input latin letters) |
|