Skip to main content

Configuration

This page covers the ongoing configuration options available after you have installed the app and created your first fields. If you haven't done that yet, start with the Getting Started guide.

info

All settings on this page require Jira admin or project admin permissions.

Configuring the Duration field​

The Duration field has its own configuration panel that lets you control how time values are interpreted and displayed. To open it, go to Jira settings → Issues → Custom fields, find your Duration field, and open its configuration.

Set time units​

Configure how the field translates day and week shortcuts:

  • Hours per day (default: 8) — defines how many hours 1d represents. For example, if your team works 6-hour days, set this to 6.
  • Days per week (default: 5) — defines how many days 1w represents.

These settings affect both input parsing and display formatting.

Choose plain number interpretation​

Decide how the field interprets a plain number (for example, when a user types just 30):

  • Minutes (default) — 30 is interpreted as 30 minutes.
  • Hours — 30 is interpreted as 30 hours.
warning

This setting affects all users of this field. Make sure your team knows whether plain numbers mean minutes or hours.

Set whether the field is required​

Toggle the Required field switch:

  • Off (default) — the field can be left empty.
  • On — users must enter a value; leaving it blank will show a validation error.

Save​

Click Save configuration to apply your changes. The new settings take effect immediately for all users.

Configuration options summary:

SettingDefaultRangeDescription
Hours per day81–24How many hours 1d represents
Days per week51–7How many days 1w represents
Plain number interpretationMinutesMinutes / HoursHow to interpret a bare number like 30
Required fieldNoYes / NoWhether the field must have a value
info

The Time Tracking field type does not have a separate configuration panel — it uses the same time-unit settings as Jira's built-in Time Tracking.

Advanced configuration​

Once your fields are set up and working, these topics cover more advanced admin scenarios.

Multiple time tracking fields on one issue​

If your teams need separate time buckets (for example Dev Estimate and QA Estimate) but you still want a combined total in Jira's native Time Tracking, configure a bucket set to sync them automatically.

Multiple time tracking fields on one issue

Require time to be logged (workflow validator)​

Add a workflow validator that blocks 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 in both company-managed and team-managed projects.

Require time to be logged (workflow validator)

Next steps​

Use Time Tracking fields

Use Duration fields

Search & Reporting