> For the complete documentation index, see [llms.txt](https://teranoapps.gitbook.io/time-tracking-custom-field/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teranoapps.gitbook.io/time-tracking-custom-field/product-tour.md).

# Product Tour

The app provides two field types: a full **Time Tracking** field and a simpler **Duration** field. This tour walks you through both so you can see them in action before diving into configuration.

***

## Time Tracking field

### Creating your first Time Tracking field

{% stepper %}
{% step %}
**Choose the field type**

Go to **Jira settings → Issues → Custom fields** and create a new custom field. In the field type list, select **Time tracking**.
{% endstep %}

{% step %}
**Name and assign to screens**

Give the field a clear name, for example **"QA Estimate"**, and add it to the appropriate **screens** (Create, Edit/View, and optionally transition screens) for the projects where you want to use it.
{% endstep %}
{% endstepper %}

From this moment on, users will see the new Time Tracking field in those projects and can start working with it just like Jira's original time tracking. For more details, see the [Getting Started](/time-tracking-custom-field/getting-started.md) page.

***

### Using the field when creating an issue

When you create a new issue in a project that has your Time Tracking field (for example **QA Estimate**):

1. Open **Create issue**.
2. In the form, you'll see an **Original estimate** input for your Time Tracking field.
3. Enter the planned time using Jira-style duration format, for example:\
   `30m`, `2h`, `1d`, `1d 3h`, `2w 1d`.
4. Create the issue.

Internally, this value becomes the **original estimate** for that specific field, and the **remaining time** is set to the same value. Users simply see a friendly duration; you get structured data for reporting.

***

### Using the field on existing issues

On an existing issue that has a Time Tracking field, you will see the same field (for example **QA Estimate**) with:

* the **original estimate**,
* the **logged (spent) time**,
* and the **remaining time**.

Typical behaviour:

* If you **log time** through the field's editor, the **time spent** increases and the **remaining time** is reduced automatically (mirroring Jira's built-in Time Tracking).
* You can also **adjust the estimate** directly if plans change (for example, increase the original/remaining estimate when you discover more work).

***

### Quick look at search & reporting

Each **Time tracking** field is a real, searchable time dimension in Jira. In **Advanced search (JQL)** you can type the field name, for example:

> `"QA Estimate".`

and Jira will suggest all aliases, such as `OriginalEstimateSeconds`, `TimeSpentSeconds`, `RemainingEstimateSeconds` (numeric, in seconds) and their string counterparts `OriginalEstimate`, `TimeSpent`, `RemainingEstimate`.

Two simple JQL examples:

**Issues with a high remaining QA estimate** (more than 4 hours)

```jql
"QA Estimate".RemainingEstimateSeconds > 14400
```

**Issues where QA time is almost used up** (less than 1 hour left)

```jql
"QA Estimate".RemainingEstimateSeconds < 3600
```

The full list of aliases and more examples are described on the [**Search & Reporting**](/time-tracking-custom-field/search-and-reporting.md) page.

***

## Duration field

If you don't need the full original / spent / remaining workflow, the app also provides a simpler **Duration** field type. It stores **a single time value** — perfect for SLA limits, time budgets, meeting durations, or any scenario where you just need one duration without work logging.

{% hint style="info" %}
**Duration vs Time Tracking in a nutshell:** Duration stores one value, Time Tracking stores three (original, spent, remaining). For a detailed comparison, see [Two field types, one app](/time-tracking-custom-field/readme.md#two-field-types-one-app).
{% endhint %}

### See it in action

This interactive demo walks you through the full flow — from creating a Duration field, through adding it to screens, to using it on a real issue.

{% embed url="<https://app.arcade.software/share/SwH6CafjyvNYScInsj7B>" fullWidth="true" %}
Duration field — from setup to first use
{% endembed %}

### Creating a Duration field

{% stepper %}
{% step %}
**Choose the field type**

Go to **Jira settings → Issues → Custom fields** and choose **Create custom field**. In the field type list, select \* *Duration*\*.
{% endstep %}

{% step %}
**Name and assign to screens**

Give the field a name, for example **"SLA Limit"** or **"Meeting Duration"**, and add it to the appropriate **screens** for your projects.
{% endstep %}
{% endstepper %}

***

### Using the Duration field

When creating or editing an issue, you'll see a single input where you can enter a duration:

* Use the same Jira-style format: `30m`, `2h`, `1d 3h`, `2w 1d`.
* Plain numbers are interpreted as minutes or hours, depending on configuration.

After saving, the field displays the formatted value on the issue view:

***

### Auto-normalization

The Duration field automatically normalizes your input. For example, if you enter `90m`, the field converts it to `1h 30m` after you save or leave the input.

{% hint style="info" %}
Normalization depends on the field's **hours per day** and **days per week** settings. With the default of 8 hours per day, `10h` normalizes to `1d 2h`. See [Configuration](/time-tracking-custom-field/configuration.md#configuring-the-duration-field) for details.
{% endhint %}

***

### Quick look at search & reporting

Like Time Tracking fields, Duration fields are fully searchable in JQL. If your field is called **SLA Limit**, you can use:

**Duration exceeds a threshold** (more than 4 hours)

```jql
"SLA Limit".DurationSeconds > 14400
```

**Duration contains a specific unit**

```jql
"SLA Limit".Duration ~ "2w"
```

For the full list of aliases and more examples, see [**Search & Reporting**](/time-tracking-custom-field/search-and-reporting.md).

***

## Next steps

{% content-ref url="/pages/g3hqfnssMpFQyOuheFMW" %}
[Use Cases & Best Practices](/time-tracking-custom-field/use-cases-and-best-practices.md)
{% endcontent-ref %}

{% content-ref url="/pages/4ogxhTSNoXzih4Rqn6QU" %}
[Getting Started](/time-tracking-custom-field/getting-started.md)
{% endcontent-ref %}

{% content-ref url="/pages/6w425lHclRfD32iGma1n" %}
[Configuration](/time-tracking-custom-field/configuration.md)
{% endcontent-ref %}

{% content-ref url="/pages/6LJ2VJ6MbD6ZkDsaDwqS" %}
[Use Time Tracking fields](/time-tracking-custom-field/user-guide/use-time-tracking-fields.md)
{% endcontent-ref %}

{% content-ref url="/pages/9LfENLgpBBif5Na29Onv" %}
[Use Duration fields](/time-tracking-custom-field/user-guide/use-duration-fields.md)
{% endcontent-ref %}