Tempo Ideas

Problem Statement

Currently, planned time and logged time behave as disconnected data points, even though both belong to the Tempo ecosystem and are intended to support resource planning and work tracking together.

While logged time is automatically aggregated and reflected in Jira tracking, planned time is not aggregated across multiple plans and does not integrate natively with Jira estimation fields.

This creates a major gap for project and portfolio management use cases.

Current Challenges

• Multiple plans on the same issue are not automatically summed.

• No native field exists to show total planned hours per issue.

• Planned time does not map to Jira Original Estimate.

• Logged time does not deduct from planned time automatically.

• No native Planned vs Actual tracking.

• Customers must rely on complex Jira Automations and custom fields to achieve standard project tracking behavior.

Expected Behavior

The integration should work similarly to Jira’s native time tracking logic:

• Planned Time → maps to Original Estimate

• Logged Time → updates Time Spent

• Remaining Estimate → calculated automatically

Additionally:

• Multiple plans on the same issue should aggregate automatically.

• A native “Total Planned Time” field should exist.

• Users should be able to compare Planned vs Actual effort directly from the issue view.

• Capacity planning and execution tracking should work together seamlessly.