> 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/getting-started.md).

# Getting Started

This page walks you through the fastest way to get Time Tracking Customfield up and running in your Jira Cloud site — from installation, through creating your first field (Time Tracking or Duration), to verifying that everything works on a real issue.

## Who this guide is for

Use this guide if you are:

* A **Jira admin or site admin** responsible for installing Marketplace apps and creating custom fields.
* A **project admin** who will add the new field to project screens and help teams adopt it.

End-users (developers, QA, support agents) generally don't need to follow these steps — once the field is installed, added to screens, and configured, they can just start using it. See the [User Guide](/time-tracking-custom-field/user-guide.md) instead.

***

## Prerequisites

Before you begin, make sure:

* You are working on a **Jira Cloud** site (the app is not designed for Server/Data Center).
* You have **Jira admin / site admin permissions** so you can install apps and manage custom fields.
* Your organization allows the installation of **Atlassian Marketplace apps** (no global restrictions or blocked installation).

{% hint style="info" %}
You do **not** need to change the global Time Tracking provider. The app works alongside Jira's native Time Tracking, not instead of it.
{% endhint %}

***

## Quick setup

{% hint style="info" %}
**Prefer a visual walkthrough?** Watch the [interactive demo on the Product Tour](/time-tracking-custom-field/product-tour.md#see-it-in-action) to see the full setup flow in action before following the steps below.
{% endhint %}

{% stepper %}
{% step %}
**Install the app from Atlassian Marketplace**

In Jira, open the apps section (for example **Apps → Explore more apps / Add apps**) and search for **"Time Tracking Fields for Jira"**.

Open the app listing, start a **Free trial** or **Install**, confirm permissions, and wait until the app appears under ***Manage apps***.

After installation, Jira will expose two new custom field types provided by the app: **Time Tracking** and **Duration**.
{% endstep %}

{% step %}
**Create your first field**

Go to **Jira admin settings → Fields → Fields** and choose **Create new field**.

{% hint style="info" %}
You'll see two field types from this app: **Time Tracking** (full estimate / spent / remaining workflow) and \*\*Duration \*\* (single duration value). Choose the one that fits your use case. See [Two field types, one app](/time-tracking-custom-field/readme.md#two-field-types-one-app) for help deciding.
{% endhint %}

Select the field type, give it a meaningful name (for example "QA Estimate", "SLA Limit", "Meeting Duration"), optionally add a short description, and save.

You can create more fields later using either type.
{% endstep %}

{% step %}
**Add the field to screens**

Right after creation, Jira may ask which **screens** to associate with the field; pick at least one project's **Create** and **Edit** screens.

If needed, you can later go to **Jira settings → Issues → Screens**, edit a screen, and add the field manually.

For real usage, add the field to:

* Create Issue screen
* View/Edit Issue screen
* (Optional) workflow transition screens and service project request types
  {% endstep %}

{% step %}
**Quick verification**

Create a **test issue** in a project where the field is on the screens and enter a duration into the new field.

Open the issue view and check that the field is visible and formatted like a Jira time value.

Then open **Advanced search (JQL)**, start typing the field name, confirm that it appears in autocomplete, and run a simple filter to ensure issues with a value are returned.

If this works, the field is correctly installed and ready to roll out to more projects and teams.
{% endstep %}
{% endstepper %}

***

## Rollout tips

* Use **clear, consistent names** ("Dev Estimate", "QA Estimate", "SLA Limit") so users understand the purpose of each field.
* Add the field only to projects that actually need it to avoid clutter.
* Send a short note or show a quick demo so users know where the field lives and how it differs from the built-in Time Tracking field.

{% hint style="success" %}
That's it — your first field is live. Share it with your team and start tracking time.
{% endhint %}

***

## Next steps

{% 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 %}