> For the complete documentation index, see [llms.txt](https://teranoapps.gitbook.io/time-tracking-custom-field/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teranoapps.gitbook.io/time-tracking-custom-field/changelog.md).

# 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="2026-06-11" %}

## Timesheet — My week

A new **Timesheet** page (Apps → Timesheet) shows your week as an issue × day grid.

* **All your time in one place** — native Jira worklogs and Time Tracking field worklogs, merged so nothing is double-counted.
* **Log from the grid** — click any cell to add an entry; a billable toggle for Time Tracking field targets.
* **Edit and delete** — fix any entry without leaving the page.
* **Add row** — search any issue and log against native time tracking or any Time Tracking field.
* **Week navigation** — previous / next / today, with daily, per-row, and weekly totals.
  {% endupdate %}

{% update date="2026-05-18" %}

## Cross-project time report

A new **Cross-project time** dashboard gadget aggregates time logged across every project you can see.

* **Group by project** — total time logged per project, ranked highest first.
* **Per-user breakdown** — optionally expand each project into a per-user split (toggle in settings).
* **Time range** — this week, last week, this/last month, last 7/30 days.
* **Billable filter** — limit the report to billable or non-billable worklogs.
* **JQL scope** — narrow to specific projects or sprints; leave empty to scan everything (capped at 500 issues).
* **CSV export** — download the breakdown for billing and audits.
  {% endupdate %}

{% update date="2026-05-07" %}

## Timer / Stopwatch

Track time on Time Tracking fields with a built-in **Start / Stop** timer.

* **Start timer** button on every Time Tracking field in the issue view.
* Stop opens the **Log work** modal pre-filled with elapsed time, date, and billable preference — adjust and save.
* Timers persist across browser tabs, devices, and reloads (stored as Jira issue properties).
* Multiple timers can run in parallel across different issues / fields.
* Long-running timer warning when elapsed exceeds 8 hours.
* See [Timer](https://github.com/mivchal333/time-tracking-customfield/blob/main/docs/user-guide/timer.md) for the full user guide.
  {% endupdate %}

{% update date="2026-04-26" %}

## Billable / Non-billable worklogs

Mark each worklog as **Billable** or **Non-billable** and slice your time data accordingly.

* **Toggle on log work** — a Billable switch on the log-work modal (default: Billable).
* **Toggle on edit** — flip the flag when editing an existing worklog.
* **Activity badges** — each worklog shows a Billable / Non-billable badge; legacy entries (created before this release) render no badge so historical accounting is preserved.
* **Activity filter** — filter the activity view by All / Billable / Non-billable; CSV export honours the selected filter.
* **Dashboard gadget filter** — restrict the gadget's aggregation and CSV export to billable or non-billable rows only.
* **CSV column** — the export now includes a `Billable` column with `Yes` / `No` / blank.
  {% endupdate %}

{% update date="2026-04-15" %}

## Decimal duration input

Duration fields now accept **decimal amounts** in addition to whole numbers.

* **Decimal tokens** — enter values like `1.5h`, `0.25d`, `0.5w`, or `2.5m`. They convert against your configured hours-per-day and days-per-week.
* **Decimal plain numbers** — `1.5` is interpreted as minutes or hours per the field configuration.
* **Combinable** — mix decimals with integer tokens, e.g. `1.5h 30m`.
* **Existing formats unchanged** — all integer inputs continue to work exactly as before.
  {% endupdate %}

{% update date="2026-02-07" %}

## 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.
* **Works everywhere** — issue create, issue view, transitions, and customer portals.

{% content-ref url="/pages/9LfENLgpBBif5Na29Onv" %}
[Use Duration fields](/time-tracking-custom-field/user-guide/use-duration-fields.md)
{% endcontent-ref %}
{% endupdate %}

{% 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="/pages/VB1wPX4m4SoPpn8VNbXX" %}
[Require time to be logged (workflow validator)](/time-tracking-custom-field/configuration/require-time-to-be-logged-workflow-validator.md)
{% 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="/pages/WS4xEQOAz1pHE4lzkEJH" %}
[Multiple time tracking fields on one issue](/time-tracking-custom-field/configuration/multiple-time-tracking-fields-on-one-issue.md)
{% 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="/pages/6LJ2VJ6MbD6ZkDsaDwqS" %}
[Use Time Tracking fields](/time-tracking-custom-field/user-guide/use-time-tracking-fields.md)
{% endcontent-ref %}
{% endupdate %}
{% endupdates %}