Skip to main content

Multiple time tracking fields on one issue

This page explains how to use multiple Time Tracking fields together with Jira's native Time Tracking by configuring a sync between them in a project.

The idea is simple:

  • You can have several custom time tracking fields on one issue (for example Dev Estimate and QA Estimate).
  • You tell the app that these fields should roll up into Jira's Time Tracking.
  • The app then keeps Jira's original Time Tracking in sync with the sum of these fields.

How syncing to Jira Time Tracking works​

A Time Tracking sync group (also called a bucket set) is a collection of Time Tracking custom fields whose values are treated as one combined total in a project.

When such a sync is configured:

  • The Remaining on Jira's original Time Tracking field becomes the sum of Remaining from all Time Tracking custom fields in the group.
  • The Time spent on Jira's original Time Tracking field becomes the sum of Time spent from all fields in the group (via worklogs added through those fields).

In other words, the sync group is the sum of your Time Tracking custom fields (for example Dev Estimate and QA Estimate), and Jira's built-in Time Tracking shows the combined time spent and remaining across all of them.

Diagram showing how individual field values (time spent and remaining) are aggregated into Jira's native Time Tracking

App fields (time spent + remaining) aggregated

How it looks on an issue​

Once the sync is configured and the fields are added to screens:

  • On the issue you will see Dev Estimate and QA Estimate as separate fields, each showing:
    • original estimate,
    • logged time,
    • remaining time.
  • On the same issue you will also see Jira's native Time Tracking field. Its values will reflect the combined state of these fields:
    • Remaining = Remaining(Dev Estimate) + Remaining(QA Estimate)
    • Time spent includes all worklogs added via Dev Estimate and QA Estimate
Issue view showing Dev Estimate and QA Estimate fields alongside Jira's native Time Tracking with combined totals

Multiple Time Tracking fields on an issue

You still log work and adjust estimates on Dev Estimate and QA Estimate as usual; the app takes care of synchronising those changes to Jira's original Time Tracking field.

Configuring the sync in a project​

To connect your Time Tracking fields, configure a bucket set in the project where you use them.

Open project settings​

Open the project where you want to use multiple time tracking fields together, then go to Project settings.

In the left-hand navigation, find the section for the app Time Tracking Customfield and open it.

Add a new bucket set​

On the bucket sets page, click Add bucket set.

Select which Time Tracking fields should belong to this set, for example:

  • Dev Estimate
  • QA Estimate

These must be fields of type Time Tracking created earlier in Jira administration.

Bucket set configuration screen with Dev Estimate and QA Estimate selected

Adding a bucket set

Save the configuration​

Confirm and save the bucket set.

Saved bucket set configuration showing Dev Estimate and QA Estimate

Saved bucket set

From now on, for this project, any worklog added through Dev Estimate or QA Estimate will also be written into native Time Tracking worklog.

When to use bucket sets​

Use a time tracking bucket set when:

  • You want separate fields for different types of work (Dev vs QA vs something else),
  • but you still depend on native Time Tracking for reports, dashboards, or integrations.
info

With a bucket set, you don't have to choose between "one global Time Tracking field" and "separate buckets" — you can have both: detailed buckets for teams and an aggregated view that continues to feed existing Jira reports.

See also​

Use Time Tracking fields

Search & Reporting