Loadingiron390

Start the timer in Jira. Head over to Jira. You should now see a Toggl Track icon in the user interface. Clicking on it will open a popup where you can start the timer, add a time entry description, project or tags. You are now tracking time! Best Time Tracking Apps Integrated with Jira Time tracking software helps track the time employees spend on various tasks in a project. The tool automates the sharing of employee time-sheets with managers for approval.

This article was written by Kamil Beer, an Atlassian Engineer at iDalko.

Time tracking is one of the first features administrators equip their Jira with. Whether for creating customer invoices, tracking project costs, or simply reporting on who did what, the right Jira time tracking app simply makes sense when using an issue tracker. Not only for waterfall projects but also when agile transformation doesn’t happen as fast and you still need to track hours when working in Scrum. Check out this blog post to learn more about a Jira workflow for Scrum.

So the said administrator visits the Atlassian Marketplace to pick a useful Jira time tracking app. Filtering the list by the keyword “Time Tracking“, they come across a lot of apps! How can we choose the best app that fits our workflow and requirements?

This article introduces and compares several great apps that do the job just right. It will explain their pros and cons and cover the whole price range from budget solutions to enterprise ones. We will be evaluating the apps on Jira Software Server, as all of them are already Cloud and Data Center compatible.

Note: These scores and the number of implementations are based on March 2020 values.

Timesheet Tracking for Jira – Free (almost)

• User Score: 3.8 stars
• Implementations: 3794+

Timesheet tracking for Jira has been around for almost 3 years now and has gained traction as one of the top-rated free apps for Jira. It fell from this position as it became paid from the version 3.7.13.1.

The app provides a simple, fast and easy to use interface called „Quick Timesheet“, where you can display a „Table report“. It allows reporting per project, per Jira group, per issue filter, and with a custom date range. You can display the worked time in either hours or days and then export it into a comprehensible excel or CSV report. The second display option is a „Calendar report” which shows your already logged work logs and recently visited issues for fast logging.

Ease of use is the key here; the UI is simple and comprehensible, and there are no alternative logging screens or anything to clutter the experience. My only complaint is about a window that kept notifying me about the number of work logs each time I generated the table report (in a similar way Jira notifies you about reindexing). But this is a minor quibble and only appeared in the paid version.

Timesheet tracking for Jira is a great start if you need some basic work log reporting in Jira. Even though the app is paid now, Jira administrators can still download the free version (2.8.7.1, Jira 8.7 compatible) from the Atlassian Marketplace. It was also the version used for this review.

It’s tough to say how the paid model of the app will compete against its time tracking rivals that had been functioning for a longer time. It’s not yet known whether it will be another Jira Suite Utilities, continually fighting an uphill battle against the better JMWE competitor as it stopped being free to use.

You can get this app here.

Timesheet Reports and Gadgets – Budget Pick

• User Score: 3 stars
• Implementations: 9413+

Having been developed for 10 years, Timesheets Reports and Gadgets is certainly one of the veterans on the market. When you install the app, you won’t see an extra menu on the navigational panel as you would with the other apps. Instead, the reports are available in the „Reports” section of a Jira project, titled as “Other”. You have three reports available – Project Pivot, TimeSheet, and Time spent.

The Timesheet report shows you a timeline of worked hours on a certain project, while the Project Pivot report focuses more on the sum of the time logged on each of the project’s issues instead of showing you a whole timeline like the Timesheet report.

You can configure a per-user, group, project, issue filter, and even a per-project role/priority report. Many other criteria are configurable including grouping the work logs by fields like Components or Versions, for instance, to see how much work your team allocates to a certain version or a certain Customer. A big plus is also the ability to include various issue fields on the issues that the users logged their work on, which makes creating custom reports much easier.

Custom reporting is certainly one of the strengths of TRG. This might be intimidating to everyday users as there are over 21 options you can tinker with in the Timesheet report. After you create your report, you can put it on your Dashboard in the form of a gadget (or as a browser bookmark). You can export it as a proper Excel report, to CSV or subscribe to it via email. Available integrations are REST API with an XML or JSON endpoints, using the regular Jira API calls.

TRG feels more like an app for projects and team leads than for regular everyday users, although they can certainly use it if they find their way around the many report options. It lacks a bit when it comes to its UI, which reminds us of Jira 6 and has a certain “retro“ feeling to it. However, coupled with the low price and high customizability, it is your app if you have either basic or advanced timesheet needs.

Try out Timesheet Reports and Gadgets.

Timetracker: Time Tracking & Reporting – Midrange Pick

• User Score: 3.2 stars
• Implementations: 1648+

Timetracker has been developed for more than 3 years. The price rises steeply here over TRG. And for 25-50 users, it stays the same as the paid version of Timesheet tracking (with the more feasible choice being Timetracker, as we will read soon).

When you click the “Timetracker” section in the navigational panel, an app wizard shows up that allows users to customize their Timesheet view. For example, the hour format is a progress indicator that shows how many hours are already logged and how many are yet to be logged.

You can log the time via the “Timetracker“ feature or in the Jira issues on a new “Timetracker” panel. Unlike the previous apps, you can log several days in a row with the “Period” parameter. The app then asks you about “Steps” – their use and connection to the Period parameter isn’t very intuitive and feels confusing. You can also add your own work log attributes when logging time, such as the type of work or the name of a client.

The reporting features a “Table”, a daily list of logged work per user with a custom time range, and a “Timesheet” suitable for both user or project reporting as it sums work done per project/user/issue. The “Chart” view shows the ratio of the logged hours between issues, users, or projects. A noteworthy feature is the “Calendar” view, showing a user’s work log with the possibility to switch or adjust the logs around, and the amount of time that’s still needed to be logged.

Another useful feature is that you can display how many hours users have logged and how many hours remain to be logged each day. You can export the report via excel, CSV or in a “printable” format.

Moreover, the app allows creating internal issues (to log time on vacations), setting holidays where logged time doesn’t count, and adjusting how many days in the past/future users can log work.

Some out of the box settings are a bit harder to understand, such as the inability to log time on weekends or the “Step” setting when logging time. Still, Timetracker is a user-friendly app thanks to the UI that is much clearer and more compact than its predecessors. You can navigate between various reports and settings in one place, which makes the app very easy to learn and very flexible for the project and team leads.

Timetracker is available on the Atlassian Marketplace.

Tempo Timesheets – Enterprise Pick

• User Score: 2.8 stars
• Implementations: 19978+

Three things stand out about Tempo Timesheets (TT): The long-held leading position on the Marketplace, the number of implementations, and the price which is about 100 USD for a 10-user license. It is undoubtedly the most refined, held with more scrutiny in this comparison, and the longest developed Time tracking app since 2009. The vendor’s pages state that Tempo is his specialty, so TT is definitely going to be around.

TT has many features, so let’s begin with the everyday ones. Users can view logged time in a Calendar view through a „Tempo“ menu in the nav panel. Here they can see how much time they logged and how much they have yet to log. They can also plan time for themselves, which is really useful or create work logs via a Jira issue. But here comes one of the unresolved obstacles; do you need to log work or log time?

Yes, one button shows the Jira work log dialogue while the second shows a special Tempo one. Can you guess which one shows what? The fact that the Jira window (Log work) appears next to TT features like “Add expense” doesn’t help though. However, disabling the Jira “Log work” dialogue helps alleviate this confusion. See how to do so on the Server here. The Tempo dialogue enables logging time for several days in a row and extra work log attributes. The UI is clear, elegant, and easier for the users to work with. What also helps the everyday user is the “Tracker” function that pops up and counts time as a stopwatch.

Reporting in TT is sophisticated. It has similar features as the Timetracker app, offering filtering by projects, teams, and accounts. The results are then grouped by sets of information (see the image below). They can be exported into common formats including XLSX. Too bad the excel reports are cluttered with columns you might not use at all, like attributes of the “Accounts” feature.

So what are these Accounts and other extras that TT brings onto the table? First of all, Accounts work like extra data in Jira issues through which you can create inter-project reporting in Tempo. Let’s say you have work for a client interspersed through several Jira projects; in a helpdesk, in development, and in a sales project. You assign the proper Account to each of these issues and create a TT report in this one account. Neat, right?

Tempo Timesheet also creates its own Teams, which are Tempo-specific user groups. Here you assign the users a role, an allocation, and a „Workload scheme“. This helps you set how much and when each user works, which is specifically useful for external and part-time workers. What also helps, is the Time approval feature where users can submit Timesheets to their team lead, who in turn approves/rejects them.

The UI is fresh, easy to use and users are greeted by a lightweight wizard explaining how to use the app. But whether TT is worth the top coin is a tough question. While Tempo is a leader in the Jira Time Tracking field, it had some not very pretty surprises for users in Timesheets v9, deprecating several useful features the users were accustomed to.

You can try out the Tempo Timesheet here.

If you’d also like to learn more about the best practices of using the app, read this guide.

Conclusion

There are many other apps to use for logging work in Jira, but the four above stand out with their popularity and deployment. Check out the basic features rundown and price comparison in the tables below.

For low-budget Jiras that just need to report on teams and projects, Timesheet Reports and Gadgets / Timesheet Tracking for Jira are viable options. Tempo Timesheets seem like a good idea only if you can really utilize most of their features, like accounts, approvals, and budgeting. Timetracker is a suitable pick when you need robust reporting and a pleasant UI for the users. All in all, each one of the apps is a good option depending on your requirements.

In this comprehensive guide we’ll discuss best practices, tips&tricks, Jira add-ons, configuration and everything else there is to know about Jira time tracking.

You may think you know how you spend your time being productive completing your tasks in Jira. But you might be surprised.

Unless you’re tracking time minute by minute you can’t really know.

Remember, what isn’t measured, can’t be improved. After all, if you’re not measuring, then you can’t know if changes make the situation better or actually make them worse.

Besides, if you’re not tracking targets, you can’t see how far your team is meeting deadlines.

Simply put time tracking, in conjunction with the measurement of results, is critical for optimization.

On a side note: Although time tracking is very powerful. I do not want to make it sound like it is the only tactic to improve performance. Additional tactics worth a mention include being results driven, measuring the number of tasks completed before deadline, etc.

Why time tracking in Jira is important for agile software development

Time tracking is particularly important for agile software development. And while not all Jira users follow agile, plenty of agile dev teams absolutely love Jira.

One of the most difficult tasks for project managers is to come up with realistic estimates. Using time tracking, in addition to other statistics (such as story points), you can compare tasks with similar jobs completed in the past. And hence calculate far more accurate deadlines.

Furthermore, you can absolutely automate time tracking

To note: marshaling a team to track time effectively can take time. And gamification techniques can be particularly effective in winning individuals around.

When to use a Jira time tracking reports

Here are a few examples of specific situations where time tracking can come in useful in Jira.

When you need:

• To provide records of the time spent on every issue and project
• To generate timesheets and customer invoices. And connect to payment processes for both clients and contractors.
• To enable work to be assessed and allocated based on real-time reporting
• To drive triangulation, allowing timing estimates to be created based on other similar projects
• To create visualizations of time spent across projects
• To integrate with third-party tools to further assist planning and time tracking

How to enable time tracking in Jira

First things first, time tracking is enabled by default in Jira.

So unless you’ve turned it off, then you don’t need to turn it on. But to turn it off…

Note: You’ll need to be an admin to take all of the following steps.

Disabling time tracking:

This is how you can disable time tracking in Jira:

1. Go to ‘Settings’
2. and then ‘Issues’,
3. then ‘Issue Features’
4. and then ‘Time Tracking’
5. Click ‘Deactivate’ to disable time tracking

Note: disabling time tracking, will not delete any existing data on your instance.

Enabling time tracking:

If time tracking is disabled, this is how you can enable time tracking in Jira:

1. Go to ‘Settings’
2. and then ‘Issues’,
3. then ‘Issue Features’
4. and then ‘Time Tracking’
5. Click ‘Activate’ to enable time tracking

How to configure your Jira time tracking settings

Before editing the time tracking settings in Jira, time tracking must be disabled. You can check this using the steps described above.

Note: Don’t forget to re-enable it once the desired changes have been made.

These are the simple steps to configure your Jira time tracking settings:

1. Once time tracking is off, you can edit the associated settings.
2. Select the values/formats for:

• Hours per day
• Days per week
• Time format
• Default Unit (minutes/hours/days/weeks)
• Legacy Mode* to use time tracking features as they worked before Jira version 4.2 (see additional information below regarding Legacy Mode)
• Copy Comment To Work Description

And again, once finished, do not forget to turn time tracking back on!

*Legacy Mode: By default, Legacy Mode is disabled if you installed Jira 4.2 or later without upgrading from an earlier version. However, if you upgraded a version prior to 4.2, it will be enabled by default.

With Legacy Mode disabled, users can change the ‘Original Estimate’ value irrespective of work recorded on an issue. If it is enabled, however, then users can only update ‘Original Estimate’ until work is logged on the issue. And it can not be changed after this point (unless all logs are deleted). Additionally, if enabled, then changing the ‘Remaining Estimate’ in a workflow post function will also clear the ‘Original Estimate’.

You may also need to configure Work On Issues permissions.

To do this:

1. From the ‘Time Tracking’ settings page, click the ‘permission scheme’ link to reach the ‘Permissions Scheme’ page.
2. Find the permission scheme associated with the project that you want to edit and click the ‘Permissions’ link.
3. This will take you to the ‘Edit Permissions’ page. Once there, you can review the users, groups and project roles that have permission to ‘Work On Issues’. If you’d like to add users, click the ‘Add’ button in the ‘Operations’ column.

• Work on issues
• Delete all worklogs
• Delete own worklogs
• Edit all worklogs
• Edit own worklogs

If you want to use a time tracking app, then once it is installed you can set it up from the ‘Time Tracking’ settings page.

How to generate a Time Tracking Report in Jira

These are the simple steps to creating a time tracking report in Jira for a specific project. Which is available as standard in Jira.

1. Go to ‘Reports’, then ‘Forecast & management’ then ‘Time Tracking Report’.
2. Select the fix version that you want a report on via the dropdown menu
3. and select how you want the issues to be sorted. You can sort by:
   1. ‘least completed issues’ – issues with the highest estimated time remaining
   2. ‘most completed issues’ – which have the lowest Estimated Time Remaining.
4. You can then select which Issues should be included in the dropdown. Including ‘All’, ‘Incomplete’ (excluding completed and non time-tracked issues).
5. You can also select which sub-tasks are included, choosing from:
   1. ‘Only include sub-tasks with the selected version’
   2. ‘Also include sub-tasks without a version set’
   3. ‘Include all sub-tasks’ (which includes all sub-tasks, regardless of version).

Time tracking apps for Jira

A range of time tracking plugins are available from the Atlassian Marketplace. Some of the most popular include:

Tempo Timesheets

Tempo Timesheets is “the” premium app that sets out to take the pain out of time tracking. Making the process fast and easy. And allowing teams to choose from multiple options on how to track time.

The app allows: managers to create granular reports, to quickly approve timesheets, individually or in bulk, to drill down into time spent data by client and to manage project teams by role, capacity, workload and holiday schemes. And much, much more.

Find out more about Tempo Timesheets here

Jira Time Tracking Api

Pivot Gadget

The Pivot Gadget, from iDalko, is an advanced reporting tool which allows you to quickly visualise key information.

Effectively, the app provides business intelligence capabilities within your Jira instance. It is useful for quickly creating cross tabulations across a long list of dimensions and measurements.

Find out more about Pivot Gadget here

Work Time Calendar for Jira

Work Time Calendar allows you to plan and track time from a calendar view, working with configurable timesheets.

Time Tracking For Jira

The app also comes with start/stop timers and allows you to lock periods of time and to generate and export customizable timesheets.

Find out more about Work Time Calendar here

Time Reports

Time Reports provides flexible time tracking and reporting of time spent on Projects, Epics and Initiatives, broken down by Days, Users and Issue Statuses.

The app also allows you to pivot by users and status and to create pie charts on time spent.

Find out more about Time Reports here

Note: More about how to use Jira can be read here.

Conclusion

With this information in hand, you should have complete transparency on how your team is spending their time. And where they are getting unexpectedly bogged down.

Time tracking can also power effective resource allocation. And it allows you to make better estimates of how long tasks will take in the future.

It also allows you to remain results-orientated in real time and to retain focus.

Now, back to you. What are your thoughts on time tracking functionality in Jira? Do you have any experience with apps? Do you know other apps that might be helpful? Any tips & tricks to share? I’d love to hear it! Share your thoughts in the comments below.

Recommended Reads:

• A guide to Jira workflow best practices (with examples)
• Dissecting Jira pricing: How much does a Jira license cost?
• Getting started with Trello: A Comprehensive Guide
• How to implement a Jira Migration (a step-by-step guide)
• How to set up the perfect Jira notification Scheme
• Jira Bitbucket Integration: the complete guide for 2020
• Jira Confluence Integration: The complete 2020 guide
• Key Updates of Atlassian Products 2020 (what you should know)
• Why Jira is better than Trello, even for non-developers
• 10 Expert Tips to 10x your Productivity in Jira