FAQ
Short answers to the questions Jira administrators and their teams ask most about Time Tracking Fields. Each one links to the page that explains more.
Before you install
Does Time Tracking Fields work on Jira Data Center?
No. It is a Jira Cloud app and runs on Atlassian's cloud platform only.
Do I have to change Jira's own time tracking settings?
No. The app adds its own field types next to Jira's time tracking, so the global time tracking provider and settings stay as they are. Each field has its own hours per day and days per week. See Configuration.
Should I create a Time Tracking field or a Duration field?
Create a Time tracking field when people log work against an estimate and need to see what is left; create a Duration field when you only need to store one time value, such as an SLA limit or a meeting length. A Duration field has no worklogs and no remaining time. See Use Time Tracking Fields and Use Duration Fields.
Using Time Tracking Fields
Why can't I see the field on a work item?
The field is missing from that work item's screen or its context does not include that space and work type. Check that the field is on the screens used to create, edit and view work items, and on any transition screen where you expect it, and that the field's context covers the space and work type. If it shows in some spaces but not in others, the cause is almost always the screens or the context. See the Quick Guide.
I can see the field but cannot change it. Why?
You most likely lack the Edit work items permission in that space, or the screen you are on does not include the field. On a transition, the field has to be on that transition's screen. If some people can edit and others cannot, compare their permissions in the space.
What does "Please enter duration in the correct format" mean?
The value is not in Jira's duration format. Use units after each number, for example 30m, 2h, 1d 3h or
2w 1d 4h 30m; text such as 2 hours is not read. See Use Duration Fields.
What does "Duration values must be non-negative when provided" mean?
Jira refused the save because one of the values was below zero. A Time Tracking field accepts no negative original estimate, time spent or remaining time, and a Duration field shows "Duration value must be non-negative." for the same reason. Enter the value without a minus sign.
How is a plain number such as 30 read?
In a Time Tracking field it always means minutes. In a Duration field it means minutes or hours, as the field's Plain number interpretation setting says (minutes by default). See Configuration.
Does time logged in a field count in Jira's own Time spent?
Only when you ask for it. Turn on Sync logged time to Jira Time Tracking in the field's configuration, or put the field in a bucket set in Space settings; otherwise the field keeps its time to itself. See Configuration and Combine Fields into Jira's Time Tracking.
JQL says my field or alias does not exist. What is wrong?
Put one pair of quotes around the field name and the alias together, for example
"QA Estimate.RemainingEstimateSeconds" > 0 or "SLA Limit.DurationSeconds" > 3600. Jira reads QA Estimate.TimeSpent
as a single field name, so quotes around the field name alone do not work. Check also that the field exists with type
Time tracking or Duration and that its context covers the space you search. See
Search with JQL.
My JQL runs but returns no work items. Why?
Usually the threshold or the alias does not match the data. The …Seconds aliases compare seconds, so 2h is 7200;
use them for numbers and the text aliases only for exact values. ~ on a text alias matches only the whole text, so
search with ~ on the field itself instead: "QA Estimate" ~ "2w". Start broad ("QA Estimate.OriginalEstimateSeconds" > 0)
and narrow down. See Search with JQL.
An automation rule with a time tracking condition never runs. What should I check?
Run the rule's JQL in advanced search first: if it returns no work items, the rule will not match any either. Then check that the rule's scope covers the spaces where the field is used and that its trigger fires, and read the rule's audit log for skipped work items and errors.
Does a running timer count toward time logged?
No. Reports, gadgets, the timesheet, CSV exports and JQL see only saved worklogs, so a timer counts once you stop it and save the worklog. See Track Time with the Timer.
Will my running timer survive a reload, another device or an app update?
Yes. Timers are kept on the work item, not in your browser, so a reload, another device or an update does not lose them. The app does not remind you of a timer you forgot, so check the time the dialog fills in before you save. See Track Time with the Timer.
Can I start a timer on the Create screen, in the timesheet or on a Duration field?
No. The timer is only in a Time Tracking field's dialog on the work item view, and each timer belongs to one field on one work item. A Duration field has no worklogs, so it has no timer. See Track Time with the Timer.
Does marking a worklog Non-billable change the field's time totals?
No. The flag is stored on each worklog and used only by the Custom work log filter, the export and the Team time — by user gadget. To see the billable share, add that gadget twice, one set to Billable only and one to Non-billable only, and compare the totals. See Mark Worklogs as Billable.
Do the dashboard gadgets and the CSV export include time logged with Jira's own Log work?
No. They count only the worklogs logged in the Time Tracking fields you created with the app. Duration fields hold a single value without worklogs, so they appear in neither. See Dashboards.
Why do two people see different totals on the same gadget?
Each gadget counts only the work items the viewer can see in Jira, so the same dashboard can show different numbers to different people. The CSV export follows the same rule. See Dashboards.
Can I pick my own start and end dates in a gadget?
No. Team time — by user and Cross-project time — by project offer six preset ranges, from This week to Last 30
days. Budget burn and Field distribution have no range: put a period in their JQL filter instead, for example
sprint in openSprints() or updated >= -30d. See Dashboards.
Which time zone do the gadgets and the export use?
UTC. A gadget's week starts on Monday at 00:00 UTC, so far from UTC Last 7 days or Last 30 days give a cleaner
rolling window. The export's Started At column is a UTC timestamp, such as 2026-11-17T08:30:00.000+0000. See
Dashboards and Export Worklogs to CSV.
Why does a gadget say "Result may be incomplete"?
The gadget reads at most 500 work items and found more, so its totals cover the first 500. Narrow the JQL filter or pick a shorter time range. See Dashboards.
Why is someone missing from the Team time gadget?
They logged no time in that field during the range, the JQL filter leaves out their work items, or Max users shown (10 by default, up to 25) cut the list. The total still counts everyone. See Team time — by user.
Why does Budget burn show "No estimate"?
The field has no original estimate in the work items the gadget read. The time spent still counts, but there is no bar or percentage. See Budget burn — Estimate vs Actual.
Why do all the columns of the exported file end up in one column?
The columns are separated by semicolons. Import the file into your spreadsheet and choose the semicolon as the separator. See Export Worklogs to CSV.
Can I export only billable worklogs?
Yes. On a work item, choose Billable under Actions → Filter in the Custom work log tab before you export; the Team time — by user gadget exports according to its Billable setting. See Export Worklogs to CSV.
Administration
Where do I change how many hours a day or days a week a field counts?
In the field's own configuration: Jira admin settings → Fields → Fields, the field's Actions menu, Contexts and default values, then the context's configuration. Each field has its own Hours per day (8 by default) and Days per week (5 by default); Jira's own time tracking settings do not change them. See Configuration.
Why is there no Timer section in a field's dialog?
The timer is off until a space administrator turns it on for the space, in Space settings → Apps → Time Tracking Customfield → Features. See Track Time with the Timer.
Does the Require time to be logged validator count time logged in a Time Tracking field?
It counts Jira's own time spent. A field's time counts there when the field's Sync logged time to Jira Time Tracking setting is on or the field is in a bucket set; time logged with Jira's own Log work counts too. See Configuration.
Data and security
Where does the app keep our time data?
In Jira. Field values are Jira custom field values, and the worklogs and timers of each field are stored on the work item. The app's own storage at Atlassian holds only each space's bucket sets and timer setting. See Data & Security.
Does any data leave Atlassian?
No. The app runs on Atlassian's cloud platform, connects to no other server and sends no analytics. CSV exports are built in your browser. See Data & Security.
Who can see the worklogs logged in a field?
Anyone who can see the work item in Jira. Only the author can edit or delete a worklog, with Jira's Edit own worklogs and Delete own worklogs permissions. See Data & Security.
What happens to the fields and their values if we uninstall the app?
The fields disappear from Jira with their values. If you reinstall the app within 30 days, Jira brings them back with their previous data; after that the data is gone. Export the worklogs you need first. See Data & Security.