Skip to main content

Changelog

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

info

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

Release: 2026-05-18​

Cross-project time — by project dashboard gadget​

See where your team's time went across every Jira project — directly on a Jira dashboard, ranked by total time logged.

  • One row per project — project avatar, name, total time logged, and a progress bar sized to each project's share of the grand total. Projects are sorted descending, so the busiest sits at the top.
  • Optional per-user breakdown — toggle on to expand each project into per-user sub-rows with avatar, name, time logged, and a bar sized to the user's share of the project total.
  • Multi-field aggregation — combine up to 10 Time Tracking fields into a single per-project number (for example Dev + QA + Contract Hours rolled up together).
  • Time range presets — This week, Last week, This month, Last month, Last 7 days, Last 30 days. All ranges computed in UTC.
  • Billable filter — restrict aggregations to billable, non-billable, or all worklogs — handy for invoiceable vs internal utilization views.
  • JQL scoping — narrow the portfolio to a client list, a business unit, or any JQL clause; the gadget automatically scopes worklogs to the selected time range.
  • CSV export — download the per-project (and per-user) breakdown for portfolio reporting, monthly leadership decks, or external invoicing.

Cross-project time — by project

Release: 2026-05-14​

Budget Burn — Estimate vs Actual dashboard gadget​

Track how much of your time budget has been spent versus estimated — directly on a Jira dashboard.

  • Estimate vs Actual per field — one row per Time Tracking field showing original estimate, time spent, remaining, and a progress bar sized to % used.
  • Over-budget warnings — rows where time spent exceeds the estimate turn red immediately, so problem areas are visible at a glance.
  • Three grouping modes — view budget burn by field (flat), by Jira project, or by assignee.
  • Multi-field support — add Dev, QA, and Contract Hours to a single gadget to compare budgets side by side.
  • JQL scoping — narrow the issue set to a sprint, epic, project, or any JQL clause.
  • CSV export — export the aggregated budget data for invoicing, audits, or external reports.

Budget Burn — Estimate vs Actual

Release: 2026-05-12​

Built-in timer​

Track time as you work without leaving the issue. Click a Time Tracking field to open the Log work modal, start the timer, and stop it when you're done — Time spent and Date started are filled in automatically.

  • Start / Stop in the Log work modal — the Timer section at the top of the modal lets you start and stop the timer with a single click. No separate panel or page required.
  • Auto-prefilled worklog — stopping the timer fills in the elapsed time and the exact moment you started. Adjust the time, add a description, flip the Billable toggle, then save as normal.
  • Survives tab close and device switch — the timer is stored on the issue, not in the browser. Close the tab, reopen the issue on another device — the same timer is still running.
  • Private by default — only you see your own running timer. Teammates and managers see only saved worklogs.
  • Per-project opt-in — disabled by default. Enable it in Project settings → Time Tracking Customfield → Timer.

Track time with the timer

Release: 2026-05-06​

Faster Log work + cleaner post-save updates​

Logging work is noticeably faster, and the field updates on screen the moment you click Save — no more brief flash of the previous value or spinners that won't go away.

  • Faster save — Log work, Edit worklog, Delete worklog, and Update Remaining are noticeably quicker. Audit and polling writes that used to block your save now run in the background.
  • Instant value preview — the field shows the value you just entered as soon as the modal closes, instead of briefly displaying the previous value while Jira catches up.
  • No more stuck spinners — fixed a race where the in-flight indicator could remain on screen until you reloaded the page.
  • Time spent auto-focused — open Log work and start typing right away, no extra click.
  • Clearer in-flight tooltip — shorter copy that tells you it's safe to close the page while the update propagates.

Release: 2026-04-29​

Edit Original Estimate from the issue view + time tracking fixes​

Original Estimate is no longer locked to ticket creation, and the totals you see in Jira's native time tracking now match what's actually in your buckets — at every stage of the issue lifecycle.

  • Edit Original Estimate from Log work / Edit worklog — set or update OE while logging time, or on its own. Useful when the PM creates the ticket but developers and testers estimate it later. Can be turned off per-instance from the Issue view configuration tab.
  • Previous estimate at a glance — the modal shows the prior OE while you edit, so changes are deliberate.
  • Correct totals from day one — issues created with bucket values populated now seed Jira's native Original Estimate immediately, instead of showing 0 until the first worklog lands.
  • Native time tracking always matches your buckets — Original Estimate and Remaining stay in sync with the bucket sum after every change, so the default progress bar stops drifting once work is logged.
  • Remaining Estimate visible in the progress popup — the per-field progress popup now shows Remaining alongside Spent.

Release: 2026-04-27​

Billable / Non-billable worklogs​

Mark each worklog as Billable or Non-billable from the Log work or Edit worklog modal. Filter the activity view, export a Billable column to CSV, and restrict dashboard gadgets to billable or non-billable scope.

  • Billable toggle — appears in the Log work and Edit worklog modals. Defaults to Billable.
  • Color-coded tags — green Billable / grey Non-billable on every activity row.
  • Activity view filter — dropdown with All / Billable / Non-billable. The activity-view CSV export follows the active filter.
  • CSV column — new Billable column with values Yes / No in both the issue and gadget exports.
  • Gadget filter — Team time — by user gains a Billable selector for utilization-vs-overhead dashboards.

Billable / Non-billable worklogs

Release: 2026-04-25​

Export worklogs to CSV​

Export worklogs logged through Time Tracking and Duration fields to a CSV file — for invoicing, audits, and external reporting.

  • Export from an issue — one-click Export CSV button on the Time Tracking panel.
  • Export from a dashboard — Export CSV button on the Team time — by user gadget, scoped to the gadget's filters.
  • 9 standard columns — issue key, summary, field name, user, account ID, start time (UTC, ISO 8601), decimal hours, formatted duration, and comment.
  • Excel / Sheets / LibreOffice ready — UTF-8 with auto-detection so Polish and other non-ASCII characters open correctly on double-click.

Export worklogs to CSV

Release: 2026-04-22​

Dashboard gadget — Team time, by user​

A new Jira dashboard gadget that shows time logged per user for any Time Tracking custom field over a chosen range.

  • Per-user breakdown — avatar, display name, formatted time, and a progress bar showing each user's share of the team total.
  • Six range presets — This week, Last week, This month, Last month, Last 7 days, Last 30 days. All computed in UTC.
  • Optional JQL filter — narrow to a project, epic, or sprint without writing worklogDate clauses by hand.
  • Per-gadget title override — drop multiple instances on one dashboard (Dev / QA / Contract) and tell them apart at a glance.
  • Row drill-down — clicking a row opens native Jira issue search pre-filtered to that user's worklogs in the range.

Dashboards — Team time — by user

Release: 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.

Use Duration fields

Release: 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).

Require time to be logged (workflow validator)

Release: 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.

Multiple time tracking fields on one issue

Release: 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.

Use Time Tracking fields