# Changelog

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

{% hint style="info" %}
The app is updated through the **Atlassian Marketplace**. Your Jira Cloud site receives new versions automatically — no manual upgrade is required.
{% endhint %}

***

{% updates format="full" %}
{% update date="2025-12-21" %}

## 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`).

{% content-ref url="configuration/require-time-to-be-logged-workflow-validator" %}
[require-time-to-be-logged-workflow-validator](https://teranoapps.gitbook.io/time-tracking-custom-field/configuration/require-time-to-be-logged-workflow-validator)
{% endcontent-ref %}
{% endupdate %}

{% update date="2025-12-01" %}

## 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.

{% content-ref url="user-guide/use-duration-fields" %}
[use-duration-fields](https://teranoapps.gitbook.io/time-tracking-custom-field/user-guide/use-duration-fields)
{% endcontent-ref %}
{% endupdate %}

{% update date="2025-11-15" %}

## 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.

{% content-ref url="configuration/multiple-time-tracking-fields-on-one-issue" %}
[multiple-time-tracking-fields-on-one-issue](https://teranoapps.gitbook.io/time-tracking-custom-field/configuration/multiple-time-tracking-fields-on-one-issue)
{% endcontent-ref %}
{% endupdate %}

{% update date="2025-10-01" %}

## 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.

{% content-ref url="user-guide/use-time-tracking-fields" %}
[use-time-tracking-fields](https://teranoapps.gitbook.io/time-tracking-custom-field/user-guide/use-time-tracking-fields)
{% endcontent-ref %}
{% endupdate %}
{% endupdates %}
