With the transition to the Forge-based version of the Time in Status app, there are important updates in how you can use JQL search queries with custom fields.
Updated Field Reference
-
If you’ve created new custom fields after updating the app, note that JQL queries must reference the new field name.
-
Old custom field names will not return results in JQL after the update.
Action required: Update your saved filters, dashboards, and automation rules to use the new custom field names.
New Comparison Support
JQL queries now support comparison operators like <, >, >=, and <= with duration-based values.
✅ Previously:
-
Comparisons only worked with numeric values (total hours as a number).
-
Syntax was limited and less intuitive.
✅ Now:
-
You can use human-readable duration formats using supported time units:
-
dfor days -
hfor hours
-
New Syntax Example:
"TIS [DEV Proj]" > 1d
This query finds issues where the time spent in the [DEV Proj] status exceeds 1 day.
Reminder: Always enclose the custom field name in quotes if it contains spaces or special characters.
Notes
-
JQL will only work with custom fields created using the updated Forge version of the app.
-
For accuracy, ensure your custom field is properly associated with the correct screen and has been recently updated (auto-refreshes every hour).
-
You can combine Time in Status fields with other criteria using standard JQL logic.
status = "In Progress" AND "TIS [Review]" >= 2h
If you need help or want to ask questions, please contact SaaSJet Support or email us at support@saasjet.atlassian.net
Haven't used this add-on yet? Try it now!