Tempo Planner

Pros

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

Cons

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

Pros

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.

Cons

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.

Pros

* 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.)

Cons

* 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.

Alternatives Considered

Reasons for Choosing Tempo Planner

Switched From

Pros

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.

Cons

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

Pros

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.

Cons

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