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.
Use cases
JWT calculated date-time fields
Title | Use case description | Label |
---|---|---|
Set the calculated field's visibility in function of the username, role or group | ||
Predicted resolution date based on business hours | ||
Predicted completion date of an epic | STAFF PICK | |
Creation date of the linked epic | STAFF PICK |
JWT calculated number fields
Title | Tech review | Style guide | Page status |
---|---|---|---|
Number of issues in the same version | DONE | DONE | COMPLETE |
Sum of Tempo billable hours | DONE | DONE | DONE |
Difference between the current date and the earliest due date | DONE | DONE | DONE |
Elapsed time between creation and resolution | DONE | DONE | DONE |
Number of open subtasks | DONE | DONE | COMPLETE |
Total time logged on an epic | DONE | DONE | DONE |
Total remaining estimate in an epic (no sub-tasks) | DONE | DONE | DONE |
Number of days an issue was in the Open status against a JWT calendar | DONE | DONE | DONE |
Number of unresolved blocking issues | DONE | DONE | DONE |
Total remaining estimate in an epic (all linked issues) | DONE | DONE | DONE |
Total of all story points in an epic | DONE | DONE | COMPLETE |
Time left before the issue is due | DONE | DONE | DONE |
Number of times a resolved issue has been rejected | DONE | DONE | DONE |
Number of times a custom field has been changed | DONE | DONE | DONE |
JWT calculated text fields
If you still have questions, feel free to refer to our support team.