Getting Started
Install Time Tracking Customfield, create your first field, add it to screens, and verify it works — in under ten minutes.
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 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).
You do not need to change the global Time Tracking provider. The app works alongside Jira's native Time Tracking, not instead of it.
Quick setup
Prefer a visual walkthrough? Watch the interactive demo on the Product Tour to see the full setup flow in action before following the steps below.
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.
Create your first field
Go to Jira admin settings → Fields → Fields and choose Create new field.
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 for help deciding.
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.
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
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.
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.
That's it — your first field is live. Share it with your team and start tracking time.
Next steps
ConfigurationUse Time Tracking fieldsUse Duration fieldsLast updated