Changelog

Release history for Time Tracking Customfield — new features, improvements, and bug fixes.

This page lists notable changes shipped with each release of Time Tracking Customfield. The most recent update is shown first.

The app is updated through the Atlassian Marketplace. Your Jira Cloud site receives new versions automatically — no manual upgrade is required.

---

December 21, 2025

Workflow validator — Require time to be logged

A new workflow validator lets admins block a transition (for example In Progress → Done) unless a minimum amount of work has been logged on the issue.

• Works with Jira's built-in Time Tracking (Time spent).

• Supports both company-managed and team-managed projects.

• Each transition can have its own minimum threshold (for example 30m, 2h, 1d 2h).

Require time to be logged (workflow validator)

December 1, 2025

Duration field type

A new, simpler field type for scenarios where you just need to store a single duration value — without the full estimate / spent / remaining workflow.

• Single-value duration — enter values like 4h, 2w 1d, or plain numbers.

• Auto-normalization — 90m is displayed as 1h 30m based on your configured time units.

• Configurable — set hours per day, days per week, plain number interpretation (minutes or hours), and whether the field is required.

• JQL aliases — DurationSeconds and Duration for search, dashboards, and automation.

Use Duration fields

November 15, 2025

Bucket sets — sync multiple fields to native Time Tracking

You can now configure a bucket set that aggregates multiple Time Tracking custom fields (for example Dev Estimate + QA Estimate) into Jira's native Time Tracking.

• Remaining on Jira's Time Tracking becomes the sum of remaining from all fields in the group.

• Time spent includes all worklogs added through any field in the group.

• Configured per project — different projects can have different bucket sets.

Multiple time tracking fields on one issue

October 1, 2025

Time Tracking custom field type

The original release of Time Tracking Customfield — a new custom field type for Jira Cloud that behaves like the native Time Tracking but can be created multiple times.

• Three values per field — original estimate, time spent, remaining estimate.

• Log work modal — enter time spent and adjust remaining, just like Jira's built-in Time Tracking.

• Six JQL aliases — OriginalEstimateSeconds, TimeSpentSeconds, RemainingEstimateSeconds and their string counterparts.

• Works everywhere — issue create, issue view, transitions, and customer portals.

• Runs on Atlassian Forge — no external servers, no data egress.

Use Time Tracking fields