Jira Cloud App
Time Tracking Fields
Add reusable Time Tracking and Duration custom fields to Jira Cloud.
Track multiple effort dimensions per issue, store SLA-style durations, and keep reporting reliable with native JQL aliases and predictable field behavior.
RUNS ON ATLASSIANFREE UP TO 10 USERS30-DAY FREE TRIAL
Problems this app solves
Remove Jira time-tracking limitations without forcing teams into fragile workarounds.
Only one native Jira time bucket
Jira Cloud exposes one built-in Time Tracking module, which limits teams that need separate estimates.
No native Duration custom field
Teams often fallback to text or number fields for SLA limits and budgets, which creates fragile processes.
Weak search and reporting quality
Non-time-native fields require parsing and manual conversion, making JQL and dashboards harder to trust.
See Time Tracking Fields in action
Recommended journey: separate buckets, add durations, aggregate totals, then enforce transition quality.
Separate estimates for each team
Feature:
Create multiple Time Tracking fields like Dev Estimate, QA Estimate, and Contract Hours on the same issue.
Benefit:
Each team tracks its own workload clearly, while project leads can still compare and manage all time dimensions.
Add Duration fields for SLA and limits
Feature:
Use Duration fields for single values such as SLA Limit, Meeting Duration, or fixed effort budgets.
Benefit:
Teams capture constraints in a clean format and keep forms simple without full estimate/spent/remaining flows.
Sync buckets to native Jira Time Tracking
Feature:
Configure a bucket set so selected custom time fields roll up into Jira native Time Tracking totals.
Benefit:
You keep granular team-level tracking and still preserve existing native Jira reports, gadgets, and integrations.
Works with Jira dashboards, exports, and automation rules
Feature:
Use indexed aliases in JQL to build reliable filters, dashboard gadgets, and automation conditions.
Benefit:
Teams can report, alert, and export using numeric second-based fields instead of fragile text parsing.
More features
Need the full configuration surface? Expand the list for advanced rollout and governance scenarios.
- Workflow validator: Require time to be logged
- Built-in time format validation (no arbitrary text values)
- Field contexts by project and issue type
- Support for Create/View/Edit and transition screens
- Service Management request form compatibility
- Forge-native architecture aligned with Jira permissions
- Configurable hours/day and days/week for duration values
Business benefits for Jira teams
The app gives cleaner operational data and stronger controls without replacing native Jira habits.
Use case playbooks by team
Use these rollout patterns to map the app to real operational goals.
Engineering and QA teams
- Track Dev and QA effort in separate fields on one issue
- Monitor low remaining QA time with JQL thresholds
- Keep release planning grounded in cleaner effort breakdowns
- Preserve global Jira Time Tracking for existing reporting
Support and service teams
- Store SLA limits as duration values in issue forms
- Standardize response and resolution thresholds by request type
- Use duration aliases in automation alerts and queues
- Reduce errors caused by free-text time values
PMO and commercial operations
- Track contract hours independently from internal delivery effort
- Export second-based fields for billing and audit reports
- Enforce minimum logged time before completion transitions
- Improve trust in portfolio-level time reporting
Rollout flow
Install and create first field
Install from Marketplace, then create Time Tracking or Duration custom field in Jira settings.
Add to screens and configure behavior
Attach fields to Create/View/Edit screens and configure Duration units or bucket sets if needed.
Operationalize with JQL and workflows
Use aliases in dashboards and automation, then add validator gates for stronger data quality.
Security and platform trust by design
The app runs in Atlassian Forge, respects Jira permissions, and keeps your time data inside Atlassian Cloud.
Time Tracking FieldsJira Cloud app by Terano Apps
Runs on AtlassianForge-nativeNo external DB
Paid via Atlassian Marketplace with free tier for small teams and a 30-day trial for larger sites.
Runs fully on Atlassian Forge
Core app logic executes in Atlassian-managed infrastructure with native cloud controls.
Data stays in Jira Cloud
Field values are stored as Jira custom field data, without external vendor-hosted replicas.
Predictable admin model
Permissions, billing, and lifecycle are managed directly in Atlassian Marketplace and Jira admin tools.
Add extra Time Tracking fields to Jira in minutes
Launch Time Tracking Fields in minutes and roll out cleaner estimates, SLA durations, and reporting-ready metrics across your projects.
Start trial on Marketplace