I find Tempo's user interface to be extremely easy to use, which makes administrating tasks a breeze. It's also very fast being embedded within Jira, which we use for our team structure and org chart by maintaining our Tempo teams. I really like how responsive Tempo is when we provide feedback on their application's functionality. With almost 2,000 people using it daily on our site alone, it has proven to be an extremely valuable and reliable tool. The initial setup was very easy, although we've added complexity over time. Having a time tracking tool directly embedded in Jira, our single source of truth, influenced our switch to Tempo, and it was by far the best option available for time tracking and capacity planning. Review collected by and hosted on G2.com.

The capacity planner side of Tempo could use a lot of improvement. While there has been significant investment in timesheets and reporting capabilities, the capacity planner seems rudimentary and basic. We've subscribed to it for many years, but it is only used by a handful of teams due to its limitations. We need capacity planning on a sprint level instead of daily or hourly, which the current tool does not support well. It needs to better handle use cases where team goals and sprint objectives are involved, taking into account the available hours after team meetings and scrums, to effectively balance workloads across individuals with different skills. Review collected by and hosted on G2.com.