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-04-26​

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