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.

I like Tempo Planner because you can navigate through the software easy.

Its a great overall software tool to have because it help business owners save money and time. Its also helps business owners stay organized with their business.

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.

The ideas behind seem fairly sound but the implementation is poor. Also, you have no idea when the plan on fixing the problems in the software since there is no communication about roapmaps or coming features.

* The integration with Jira was the main selling point. * A web interface was also something we were looking for. (We only plan on the "project" level. Planning within individual projects is handled by PMs on Jira project.)

* The software is confusing (several similar views that do different things) * Administration is a *nightmare* - really, I seen nothing as bad as this for several years: we have 25 teams, 250 "Internal" users and 200 external. Admins need to be added to each individual team (no central permissions) and if users are to see plans from other teams the 25 teams need to be updated manually each time we get a new user. * Each user has a workload scheme - but if a user's scheme i M-F: 8, 8, 8, 8, 5 and you add a 37 hour task for Monday, Tempo plans 7,4 hours per day showing the first days as under allocated and the last over allocated. Come on??? * Seems buggy. We have had a number of issues where we could not work out what we were seeing, reported a bug to Tempo - just for issues to magically disappear after a day.

His synergy with tempo timesheet to understand the difference from what you plan and what people do

The difficult to plan the issue of a SPRINT. The impossibility to see a real capacity

Tempo Planner is great for planning time in Jira. With seamless integration with the excellent Tempo Timesheets this is a fantastic addition to the Tempo family and vital in planning time for your software development team. Supports water fall and agile working methods and provides lots of tools to help your teams understand what they should be working on.

Currently lacks google calendar integration on the Server version which would be really useful in syncing meetings and planned work programmes.

It's super easy to log time within Jira. I can access time entry in a few different ways, so if I'm working on an issue, I can log it directly in the Jira task. I can also quickly run reports to assess burn and progress down to the specific issue or bug.

The search functionality within Jira is pretty awful. It works great in the mobile app, but I'm not going to use my phone to log time when everything else I do for work is in browser.

Ability to plan staffs within a team. Daily time management

It doesn't work well with estimate from JIRA. So have to re-enter

We like the integration with JIRA and the ability to download data we need when we need it.

In some of the search fields and reports finding the issues/subjects you are looking for does not seem to work consistently. There are some cases where we try to find a specific item and the search will not return it even though our search terms are accurate. We also would like to see a little more flexibility in the way we setup and plan our issues in terms of how this relates to our billing system.

It is OK and it provided partly what we need but sometimes it is a little frustrating - especially since you can't change the availability of a person during the year.

I like that you can plan the time for everyone working at the Company and I like that it interacts with JIRA. Everyone can access there available hours and what project they are working on. It is nice that Tempo Planner knows the public holidays and that it can provide an estimate of the hours people should be at work for.

What I really don't like is that Tempo Planner is not very flexible. If people's daily working hours change during the year, Tempo Planner can't deal with that. You can't provide e.g. Person A works full time from Jan-Mar and only half time after that. Once you put in full-time, you are stuck with it and Tempo Planner will calculate the total hours per year based in full time. Also, if plans change, the already planned time cannot be edited, rather needs to be deleted and newly entered.

Ease of use, the overview and the rich reporting features, as well as the integration in all Jira issue features. Very good to make detailed plans on a daily or weekly basis.

There is no change history. Often things get messed up, accidently. Then there is no possibility to investigate what happend to learn from, or to restore. Also user permissions are fairly poor - at least too poor for our team. No option to plan on a higher lever/portfolio planning.

We are trying to use it for keeping track of the workload for our personnel, but we are not fully there yet.

Even it is not so intuitive to plan the resources, the overview of planned time and utilization is nice.

As we do not plan our time in so detailed manner as the software seems to be designed for (we plan resource not on an item level, but on a Project level, and Resources do not only work in on JIRA Project, but maybe up to 5-6 different ones) it has been a bit hard to get it working, both due to bugs (now solved, I think) and limitations in the tool. As the title says, we could have wanted more from a tool like this, but still useful, and value for Money.

It's easy to setup work plans for my team and see time available

The product is ok, but the planner is tedious to use. When using the planner, it would be nice if the tool would automatically fetch the estimated time. On the issue list, it would be nice if time planned was displayed (as it was before) Some basic reports would be nice, i.e: plan vs. actual log times.

Integrates well with core jira to allow us plan work across our teams

The reporting suite isn't especially good

We use it to track time and plan sprints for our contractor resources.

I'm a fan of how it integrates well with JIRA and Tempo timesheets.

I do wish it were MORE integrated from an API perspective . I'd love more detail reporting and cross function with both JIRA, Time-sheets and really good Teams integration.

It is good to have planning and time writing from within Jira. Luckily the API gives a lot of data for us to use in an external system and to make the data for us.

We use the planner for planning holidays and general stuff like that.

The setup and onboarding was not as easy as it could be. There was a lot of searching for how to do this or that ..