Really good.

Ease to use and implement. Integrates well with other applications.

Nothing really. I am not at the stage of use of finding any limitations or gaps.

It works well for partner time tracking. Our QA vendor is generating all their timesheets right of Tempo. It is now our standard for finance audits on time keeping for this partner.

Integration to Jira is seem less and allows for my QA team to enter timecards in same system they use every day. Decent price for 250 users providing comparable function to higher cost solutions.

License integration with Jira. I have a 500 IT implementation of Jira going to 750. I only have a partner using Tempo 100 licenses. However, my license costs keep going up. I am paying extra just for Atlassian's license simplification. Rest of IT uses Planview and given this license practice raising my Tempo costs I will be forced to not renew. It would be preferable to have license audits to ensure we are not using 750 than to pay an extra $10k for licenses we will never use. If we were to sunset Planview for Tempo in next audit would true up and pay the full price so no real harm to Atlassian. Versus as it stands now you will loose Clorox Tempo business. Support is not very clear. Would recommend an implementation service to train us and help us get full potential of Tempo realized.

In conjunction with our Senior Project Manager, I tried out Tempo planner on just the project management team and did not feel it was well fit to our needs. We submitted a ticker to tempo/jira, and our needs are not able to be met (CSV esport of estimates versus actuals, very important to our workflow). Because of this, we are looking into alternatives. We are still trying to move away from Float, our current resourcing tool, but are not sure that Tempo Planner would suit us any better.

It is easy to input a block of time and the software will automatically allocate daily amounts for you.

It is not possible to hide planned time from the production team, and this planned time shows up in Tempo where team members go daily to log this time. Because the time is broken out in equal parts across the assigned time period, it is often broken into odd increments that do not fit our 15 minute increment structure. Because this is surfaced to the team, we anticipate issues with them logging planned time rather than their actuals and fussing when their actuals do not match the planned resourcing for the week (which they often do not). We also miss the capability to color code the planned work by project manager (which we had in Float). The overhead view of all resources is not as easy to break down as our previous program, Float, because it does not surface enough detail. We also cannot export the single most important report as a CSV (estimates versus actuals), which was the #1 reason we anticipated moving to Tempo planner in the first place.

Tempo Planner has really helped when relating with PMs and Service Delivery Managers for updates on resource allocation

Useful when assigning teams to different projects.

So far so good. This tool has been helpful.

We were looking for the software that can be used for planning especially in context of development resources. With Tempo we can easily book a resource for a specific task or project and anyone can see that the resource is already booked. The second way we are using it is for out of office (vacation/training/sick leave etc.) planning that gives transparency to everyone in the organization so it's easily to check who is planning to be off on a specific time.

You can plan any task in JIRA with Tempo planner, it's easy to see the overall plannig per team or individual user, planned time can be easily reported.

Sometimes confusing UI, especially if you like to see the planner from reports engine.