I can use mobile app for logging hours which is pretty convenient. It also gives you pretty neat working hours report so I can bill my clients accordingly.

Sometimes it's cumbersome to find Jira issues that I'd like to log hours in. On mobile application you cannot set worked hours directly (you can do it through website tho). You have to set specific begininning and end time which make the process longer.

We've used different time tracking software in the past, but as soon we migrated to Jira, Tempo Timesheet helped us achieve many things. Mainly: - users DO log their time! - it took very few documentation and "training" for the whole team to be on board - Our customers appreciate the level of detail we can get from reports. No need to export Jira issues to give them detail - We can easily track "hours budgets" for our customer using the API! That way, we are able to generate new revenu with our customers.

It takes no time to configure and no time to bring the team to use it. There's also so many ways to add work logs that there's no reason to lose track of time worked on Jira. Users do not need to go to a different page or app to use it. It shows up in Jira issues, as trackers directly in Chrome and there's many Jira dashboard gadget available to keep track of our teams. Reporting is extremely easy. Not only is it easy to generate reports using different filters and groups but the exporting options work very well and we use them with every invoices we create The support team is also very good! They stay in touch and do everything they can to help.

There is not much that I don't like. As any customer I do have very specific wish list for potential features and some are not available. But in the end, Timesheets does what it is suppose to do.

Its mostly fine, but if there was something that fit my needs better, I would switch.

Generally, it is fairly easy for my team to log their time, and it is good that they can log it on EPICs rather than specific issues.

It's really clunky to administer the team and projects. There's no way to automatically add new projects to the team, and add new team members by default. Most importantly, the billing model is really frustrating. We do client work, and clients have access to our Jira -- But, clients will never ever log time. I don't believe that I should have to pay for those users as Tempo users. There should be an actual per-seat billing model, where I only pay for users who use tempo.

It's pretty easy to plan the workload and track the team burnout pace.

Overall, I'd say it covers the needs. The progress Tempo development team made in past year is pretty impressive. Trackers became way easier to use. The reports are great, easy to customize.

That I can't buy the license only for the users I need tracker for. I have a bunch of people in Jira that don't need the tracker, but I'm paying for them anyway. It's a bit of a downside.

Overall very good. Support has provided quick turnaround on any questions. Bug fixes and improvements continue at a good pace, and the improvements are quality ones.

For issue-oriented end-users (e.g. developers), it's a great tool. * Easy to use * Seamlessly integration with Jira * Easy administration

For account oriented end-users, there's an impedance mismatch. These users just want to log time against an account. Logging time against an issue and then assigning it to an account never feels right to them, and it's their biggest complaint. Tempo's solution is Internal Issues, but that doesn't resolve this usability issue for these users. Does not support labor categories well - especially when a user performs different roles with different labor categories in a project. It can be partially worked around with work attributes. Reporting works great for what's built-in but still needs improvement. E.g. reports of hours by combinations of project, account, user, role, work-attributes are needed. Dumping into Excel is the workaround here.

I like that it is easy to add time from JIRA and I don't need to go to a separate application.

I wish there was an easier way to get the information from Tempo to accounting software (i.e. Quickbooks Online) currently I have to copy the information over line by line when invoicing.

I like the reports. These are very easy for me and for team leads to track the team's efforts by task and individual. However, the usage of tempo is misleading. The effort estimate used by Tempo is not basic to Jira which means it doesn't play well with others (e.g. Capacity Tracker). Therefore, my experience is somewhat negative. Should I be able to find a good reporting tool to the effort in Jira, I will probably stop using Tempo.

The reporting mostly. Time tracking is available in Jira so other than reports, I don't see much value

I'm using Capacity tracker to plan my sprints and Tempo for tracking the team's efforts. These two tools don't work well together. Moving to Tempo Planner would increase my costs by a lot.

Overall we were able to go live and start using the timesheets without too much of a problem. We like it because it is fast and love the ability to download our raw data for reporting.

The software is pretty intuitive and both fast and easy to get time entered into along with a good ability to download data for different integrations we have from the API.

Some of the documentation is hard to use and find for the current version of the software. It seems like there is a lot of old or outdated information available. When searching for issues to enter time against using the issue lookup box the search is fast but terrible. It seems really inconsistent why you get the result you do.

We use Tempo Timesheets to show how many hours we work in each issue.

It's easy to work with the Tempo for both timekeeping and information extration.

Not being able to automatically email users in case of missing timekeeping.

Tempo timesheets make very easy, with little work from project managers, to generate the billing reporting to our customers organizing cost by accounts

- Very easy tool to use for end user - The capability for reporting - Installation out of the box. No extra knowledge for any Atlassian Administrator - The organization of teams and acounts - The customization: type of accounts, new attributes, etc... - The feature for planning

The reminders policy could be improved Multiple timesheet reviewers will be very useful Non billing time like holidays or leaves it's not completely covered. Should be resolved in other way than using Internal Issues

Our employees are required to enter their time daily. Timesheets greatly simplified this process by giving them a weekly view with which to enter multiple tasks much easier.

Weekly views made entering times against projects a breeze.

Would be nice to duplicate entries across several days.

Good accountability of hours logs for financials purpouse and project management

The ease to extract various reports, user friendly for logging hours, easy use to edit logs if necessary, access priviledge

The posibiliti to extract reports filtered by multiple teams

As said Tempo Timesheets is a big contributor to our overal eco system in our company. We integrated it completely in our in-house developed ERP/Finance system. We link it with BI tooling to make the best decisions on our data.

Tempo Timesheets is the backbone of our company. We use it daily as we need the timesheets to registrate our worklogs and get paid. I like the new reporting style, the API options and the dynamic use of the software.

We can't configure a safe way for our customers to use Jira without them accessing the worklogs. As this is a big deal for us that our customers are not allowed to see the worklog before we check/manage them this is a big miss for us.

Very positive! Everyone enjoys it and I don't receive any negative feedbacks about it.

The interface is very user friendly, it allows all team members to quickly fill out their timesheets. That was our #1 requirement when we switched to Tempo Timesheets. Our previous solution made this tedious and team members would be reluctant to properly enter their time. In addition, the options at our disposal (different teams, reports, admin) allows us management to easily bubble up all required info.

Even though we consider it is worth it, it is the most expensive timesheet plugin in the Atlassian Marketplace. Also, there is a bug that annoys me personally: when logging work and navigating quickly through the fields (jumping to the "time" part with TAB), any value entered too quickly would be wiped by a refresh that happens in the background. I'm to blame as well for that because I did not report it yet. :)

Adds ease of use to worklogs in Jira but nothing more. Worklog management not improved with it and not sure if it is worth the licence fee. Looking at alternatives to help with invoicing

Adds better visibility to work logs. Allows additional data (attributes) to be stored on worklogs. Better reports

Bulk processes: Only adds (for periods). No bulk update/deletes/moves.

Tempo Timesheets has given us a much needed overall view into our Company and helped us track where we are spending our time.

The ability to have a more detailed view point of where our time is being spent.

We do have some pain points when it comes to tracking contracts and when client goes over their paid hours.

We used Jira Cloud first with Tempo. Both have being working solidly and well, without regrets. Team leads and managers have been able to easily track time spent in tasks and organize work accordingly.

Tempo is very easy, simple and intuitive to use. It does not have a lot of features, but the few that it has work solidly. The table layout allows the user to easily see what tasks they have worked on and how much work they have left to do. Also, the integration with Google Calendar is very useful and works well.

Automatic time tracking didn't work too well. It sometimes tried to suggest we log hours from already closed tasks or from tasks that we didn't even use. In addition, the service was sometimes slow in logging hours, taking several seconds to display the changes.

The ease of reporting between projects and users as well as being able to view planned time

The limitations on using custom fields for reporting

We try to use another time-tracking software but tech team sad - Only Tempo, it very easy to use

Easy and functionality Integration with GCal

You can only use with Jira but we changing project traсker to Asana must to change timesheet software

It is easy to implement, update, and create new teams.

When you select a leave date for a team member, they still see the old team lead as an option for submitting their timesheet to. It is useful to track how employees move in the company, but this can be an inconvenience. The ability to move the tracker from the right corner of the screen to another area of the screen, would also be useful. It can cover the bottom scroll bar on charts.

pretty good. We have liked using it and like that it's integrated into jira

I like the ease of integration into Jira

Reporting functionality while pretty good is a little bit limited. Would like to be able to more with querying an actual sprint or being able to do some simple math on fields. Things like grouping by an issue and showing actual time vs estimated time.

Easy to record time spent. It does its name said.

Two major concerns here, one is the price. Our company has 35-40 users using Jira. However, only 10 people max are using Tempo. But the bill of Tempo is applied to all users which is not flexible. The second concerns is the reporting. We set up a custom field to identify each business sector, but it's not easy to use this field to group time log.

For the most part Tempo is trouble-free. It allows users to log their time against JIRA issues and managers to build reports based on that data. It's largely intuituve and has few "gotchas". Users don't need to bother administrators much. We've had very few problems. Support is good.

I feel they've tried to make it too sophisticated in places when most people want only very basic functionality.

1- Sometimes after update/upgrade user settings like saved report, will be gone and user(s) have to recreate them. 2- Some issues, takes long time to addressed and resolved. 3- No support over the phone, sometimes issues are serious and emails is not the fastest way to resolved time sensitive issues

1- Easy to use 2- Easy to configure 3- Easy update process 4- Great reports