The field does not appear or is empty - checklist

Data Center This page documents Time in status, Timer, Stopwatch and Calendar fields for Jira Data Center and Server. On Jira Cloud? See Time in Status (Forge) for Jira Cloud.

ā€œThe field is not thereā€ and ā€œthe field is there but emptyā€ are two different problems with two different sets of causes. Work out which one you have first - it halves the checklist.

  • Not on the issue at all - no label, no row, nothing. This is Jira-level: screens, contexts, schemes. Start at The field does not appear.
  • On the issue but showing nothing, or showing a license message instead of a value - the label is there and the value is not. This is app-level, and the app usually names the reason itself. Start at The field appears but is empty.

The field does not appear

These are the causes that keep the field off the issue entirely. The first is about the license; the rest are native Jira behaviour that applies to every custom field, not only to this app’s.

1. The app license

As of 6.6 a missing or invalid license does not hide the field. The Time in Status field stays on the issue and shows a license message instead of the value, so if the field is gone entirely, the license is not the cause - read on. See The license message instead of a value.

Before 6.6, without a valid license the app’s fields did not render values at all, and support tickets that begin ā€œeverything stopped at once, on every projectā€ almost always ended here. Check the app’s license in Manage apps.

2. The field is not on the screen

A custom field only shows on an issue if it is on the screen used for that issue operation - view, edit, create - through the screen scheme of that project and issue type. Add the field to the right screen in Administration → Issues → Screens.

3. The issue is outside the field’s context

A Jira custom field context scopes the field to a set of projects and issue types. An issue in a project the context does not cover has no value for that field and Jira does not render it. Open the field’s contexts and confirm the project and the issue type are both covered.

To find out where your fields are actually in force - which projects and issue types each context covers - see Where the fields are used. It is faster than opening every context by hand, and it is the right first step before a cleanup or a migration.

4. A Timer or Stopwatch scheme with no projects

A scheme binds a configuration to projects and issue types. An empty list of projects means no projects at all - it is not a wildcard, and it does not mean ā€œallā€. A scheme saved with the project list left empty matches nothing, and every Timer or Stopwatch that depends on it stays inert.

Open Timer schemes or Stopwatch schemes and check that the project list of the scheme actually names the projects you expect.


The field appears but is empty

When the value is empty, the app is usually telling you why. The reason is exposed in the empty value itself - read it before changing anything.

Reason What it means What to do
NO_VIEW_ACCESS This user has no access to the field. Check the visibility conditions of the field configuration - roles, groups, users, anonymous access, and the value display JQL filter.
NO_VALUE_ACCESS This user has no access to the value. Check the Value access tab of the field configuration. As of 6.4 the lists on that tab close the value itself, not only real-time sorting in JQL.
The JQL condition did not match The field is scoped by a JQL condition that this issue does not satisfy, so nothing is counted for it. Check the JQL in the field configuration, the goal, or the value display filter - whichever applies to the field type.
No history for the tracked statuses The issue has never been in any of the statuses the field tracks, so there is nothing to add up. Confirm the tracked statuses are the ones the issue actually passes through.
Zero time The tracked interval really is zero. Nothing to fix. A transition that entered and left a status in the same instant genuinely counts as zero.
Below the format minimum The value is smaller than the smallest step the display format can render. Choose a finer time format - a format that renders down to hours cannot show a 40-second value.

The license message instead of a value

As of 6.6, without a valid license the field and the panels say so instead of going silent:

  • The Time in Status field stays on the issue and shows the message in place of the value.
  • The Timer, Stopwatch and Time in Status issue panels are shown with the same message in place of the values and the buttons.
  • The message is headed The Time in Status license is not valid. A Jira administrator reads ā€œā€¦Check the app license in Administration - Manage apps.ā€; every other user reads ā€œā€¦license problem. Please contact your Jira administrator.ā€ The texts are also translated into Russian.

Two things do not change:

  • A user who has no right to see the field still does not see it - the license message does not reveal a field that is closed to them.
  • The Timer and Stopwatch fields in the issue’s field list do not show the message - only their panels do.

What to do: check the app license in Administration → Manage apps.

Reading the table in order

The rows above are also a diagnostic order, because they separate ā€œthe user cannot see itā€ from ā€œthere is nothing to seeā€:

  1. NO_VIEW_ACCESS / NO_VALUE_ACCESS - a permissions problem. The value exists; this user is not being given it. Reproduce as a Jira administrator: administrators always see the value, so if it is populated for you and empty for them, it is one of these two.
  2. Unmatched JQL / no history - a configuration problem. The field is doing exactly what it was told, and what it was told does not describe this issue.
  3. Zero time / below the format minimum - a presentation problem. The calculation ran and produced a number that this format renders as nothing.
Lists on the Value access tab that were filled in before the upgrade to 6.4 start to take effect after the first save of the configuration. If a group of users lost the value right after a configuration was saved, open that configuration and check the audience on that tab. See the 6.4 release notes.

Values are missing only on old issues

The fields calculate from issue events in real time, and from issue history for issues that existed before the field did. If new issues are fine and old ones are empty, you are looking at the history path, not at access rights.

Run Restore timer and stopwatch by issue history over the affected JQL - it re-derives the counter from the issue history and then hands the issue back to normal real-time processing.


Search and sorting do not see the value

The field shows a value on the issue, but JQL does not find it or does not sort by it. Two separate settings govern this:

  • Value access in the field configuration decides who gets real-time calculation for sorting at all.
  • Some settings need a reindex after they change - Status Tracking, Calculate Time in Statuses and Calculate Status Categories are listed under Reindex on the field configuration page.

Still stuck

Collect, before opening a support ticket:

  • one issue key where the value is wrong or missing, and what you expected instead;
  • whether a Jira administrator sees the same thing on the same issue (this splits access from configuration in one step);
  • a screenshot of the field configuration - the tracked statuses, the calendar, and the Value access tab;
  • for a Timer or Stopwatch, the scheme that covers that project and issue type.

Then contact JiBrok support.


JiBrok time in status Time in status | SLA | Timer | Stopwatch
Migration
Release notes
Tutorials
Settings
Troubleshooting
Work calendars
Time in status
Timers and Stopwatches
Stopwatch
Timer
Additional functions
Issue panels
Reports
Field Helpers
Other fields
API
Reference information