Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

JIRA's Time Tracking feature enables users to record the time they spend working on issues (see Logging Work on an Issue).

(warning) Note: Before users can specify time estimates and log work, they must be granted the Work On Issues permission for the relevant project(s).

Disabling Time Tracking

Time Tracking is ON by default (as shown in screenshot 1 below). However, this feature can be disabled from the Time Tracking administration page.
(info) Time tracking will be OFF by default if your JIRA installation was upgraded from a version prior to 4.2 that had time tracking either disabled or never enabled.

To disable Time Tracking:

  1. Log in as a user with the JIRA Administrators global permission.
  2. Choose > System. Select Issue Features > Time Tracking to open the Time Tracking page.
    (tick) Keyboard shortcut: 'g' + 'g' + type 'time t'
  3. Click the 'Dectivate' button to turn Time Tracking OFF.

(info) You will not lose any existing Time Tracking data by disabling/re-enabling Time Tracking.

On this page:

Icon

 Time tracking add-ons for JIRA in the Atlassian Marketplace extend JIRA's time tracking power. Check them out here.

Enabling Time Tracking

To enable Time Tracking:

  1. Log in as a user with the JIRA Administrators global permission.
  2. Choose > System. Select Issue Features > Time Tracking to open the Time Tracking page.
    (tick) Keyboard shortcut: 'g' + 'g' + type 'time t'
  3. Click the 'Activate' button to turn time tracking ON.


Screenshot 1: Time Tracking is ON

Configuring Time Tracking Settings

To edit JIRA's Time Tracking settings, it must first be disabled. Once you have changed the settings, you will then need to re-enable Time Tracking so that users can log work on issues.

(info) You will not lose any existing Time Tracking data by disabling/re-enabling Time Tracking.

To configure Time Tracking settings:

  1. Log in as a user with the JIRA Administrators global permission.
  2. Choose > System. Select Issue Features > Time Tracking to open the Time Tracking page.
    (tick) Keyboard shortcut: 'g' + 'g' + type 'time t'
  3. If Time Tracking is ON (refer to the indication at the top of the Time Tracking screen), click the 'Deactivate' button to turn Time Tracking OFF.
  4. The Time Tracking settings will now be editable as shown in the following screenshot.
    Screenshot 2: Time Tracking is OFF
  5. Configure Time Tracking settings by editing the following fields:
    • 'Hours per day' — enter a suitable value (e.g. 8). You can enter fractions if you wish.
    • 'Days per week' — enter a suitable value (e.g. 5). You can enter fractions if you wish.
    • 'Time format' — select pretty/days/hours. This will determine the format of the 'Time Spent' field when an issue is displayed.
    • 'Default Unit' — select minutes/hours/days/weeks. This will be applied whenever your users log work on an issue without specifying a unit.
    • 'Legacy Mode' — select this check box if you prefer to use JIRA's time tracking features as they operated prior to JIRA version 4.2. For more details about this option, please see About 'Legacy Mode' (below).
    • 'Copy Comment To Work Description' — select this check box to ensure that any content entered into a Comment field while logging work as part of an issue operation, is also copied across to the Work Description.
      (info) When 'Copy Comment To Work Description' is enabled, your user's work log entries will be visible only to members of the project role or group selected in the padlock icon dropdown on their issue operation screen. If 'Copy Comment To Work Description' is disabled, your user's work log entries will be visible to anyone by default.
  6. Click the 'Activate' button to turn time tracking ON.
    If the permission schemes used by your project(s) already have the appropriate Work On Issues permissions, then there is no need to proceed any further.
    However, if you need to configure these permissions, proceed with the remaining steps below:
  7. Click the 'permission scheme' link as shown in screenshot 1 (above). The 'Permissions Scheme' page will be displayed.
  8. Click the 'Permissions' link of the permission scheme associated with the project(s) where you wish to specify Work On Issues permissions. The 'Edit Permissions' page is displayed for your chosen permission scheme.
    (info) See Managing Project Permissions for details about the various permissions.
  9. Check whether the row labelled 'Work On Issues' contains the appropriate users, groups or project roles who need to specify time estimates or log work. If it does not, click the 'Add' link in the 'Operations' column:
    Screenshot 3: Time Tracking Permissions
  10. Select the users, groups or project roles to whom you want to allow time tracking and work logging on issues.
  11. Click the 'Add' button.
  12. If it is needed to enter the 'Original Estimate' during issue creation or during issue editing, ensure that the field 'Time Tracking' is added to the relevant screens associated with those operations. Refer Associating a Screen with an Issue Operation for more details.

About 'Legacy Mode'

  • If Legacy Mode is disabled, your users will be able to change the Original Estimate value irrespective of any work being logged on an issue. Legacy Mode is disabled by default on new installations of JIRA version 4.2 or later.
  • If Legacy Mode is enabled, your users can only specify an Original Estimate before they start logging work on an issue. This value cannot be changed once any work has been logged, unless all work logs for that issue are first deleted.
  • By default,
    • Legacy Mode is disabled if your JIRA 4.2 installation was conducted cleanly (that is, without upgrading from an earlier version of JIRA).
    • Legacy Mode is enabled if you upgraded JIRA from a version prior to 4.2.
  • With Legacy Mode enabled, if you change the Remaining Estimate field in a workflow post function the Original Estimate is also cleared. This issue is tracked at  JRA-25031 - Time Tracking Legacy Mode and Workflow Post Functions Error Open
  • Please refer to the Logging Work on an Issue and the JIRA 4.2 Release Notes for more information about logging work and modifying time estimates.

Related Topics

38 Comments

  1. How do we REQUIRE time tracking before our user resolves an issue?  I try adding "Log Work" "Time Spent" or "E Time Spent" as a workflow transition validator, but I always get an error message, any of:

    An unknown exception occured executing Validator com.googlecode.jsu.workflow.validator.FieldsRequiredValidator@1b23d42b: root cause: [GenericEntity.get] "worklog" is not a field of Issue

    An unknown exception occured executing Validator com.googlecode.jsu.workflow.validator.FieldsRequiredValidator@2baff0c9: root cause: [GenericEntity.get] "aggregatetimespent" is not a field of Issue

    Etc.

    The "Log Work" is right there on the resoluton screen, so the claim that whatever is not a field of Issue strainsmy credulity ...

    UPDATE: ObSolution: http://dannyman.toldme.com/2011/12/01/jira-jython-validator-enforce-time-spent/ with the Jython Plugin, every problem becomes a Validation hook. (smile)

    1. As of JIRA 5.0 you can require the Log Work field.  That will, however, mandate that you enter at least 1 minute of time spent - 0 is not allowed.

      1. How would I do that? And just to clarify, it only applies to those users with the 'Work On Issues' permission yes?

        1. Administration > Issues > Fields > Field Configurations > Default Field Configuration

           

          Find the Time Tracking entry and click on the Optional text which will then change to Required.

           

          The worked field will then be required.

    2. In our environment, we require that Original Estimate be >0 before an issue can be assigned. When an issue is Resolved, we require that Remaining Estimate be 0.  In these cases the Workflow option for Assign or Resolve won't even show up if the above criteria is not met.  (I will admit that it's confusing to people early on about why those buttons aren't there, but I finally have them 'trained'.)

    3. In our environment, we require that Original Estimate be >0 before an issue can be assigned. When an issue is Resolved, we require that Remaining Estimate be 0.  In these cases the Workflow option for Assign or Resolve won't even show up if the above criteria is not met.  (I will admit that it's confusing to people early on about why those buttons aren't there, but I finally have them 'trained'.)

    4. In our environment, we require that Original Estimate be >0 before an issue can be assigned. When an issue is Resolved, we require that Remaining Estimate be 0.  In these cases the Workflow option for Assign or Resolve won't even show up if the above criteria is not met.  (I will admit that it's confusing to people early on about why those buttons aren't there, but I finally have them 'trained'.)

  2. Our time tracking doesn't seem to be functioning properly. If we designate an issue to take 3 days of work and the developer puts in 2 days and 4 hours logged, Jira shows 0 time remaining. It should show 4 hours remain. Our configuration is 5 work days, 8 hours a day, default unit minutes. Is there a bug?

     

  3. Anonymous

    Is it possible to track time automatically when a user just start progess and stop progress? i dont want to be adding log works. Just start and stop work.

    Thanks

    1. Anonymous

      I would also like to have something like the idea above. And a global Button to pause all work prefered next to the search field.

    2. Anonymous

      Automated Log Work plugin records time difference between clicking Start and Stop button and adds calculated value to Jira Log Work. It partially covers your needs and makes the whole process much easier because you don't have to count time manually. The plugin is free.

      1. Automated Log Work since version 2.0 is able to track time automatically when user hits Start/Stop Progress default JIRA buttons (all actions from default workflow are supported).

    3. The tempo plug-in provides a capability like this.

  4. Anonymous

    This is all good - but I don't see how an admin can see the tracked time across all projects see a project's/issue's logged time across all the various team members working on that project. Is there something here I'm missing?

    1. += 1

      I've played around with plugins that do some time tracking/reporting.  However, I would like to see examples of time-tracking reports using custom filters over arbitrary periods.

      For instance, if I have a filter for issues in multiple projects during Sprint 3 (a four-week sprint that crosses month or quarter boundaries), I'd like to see how much time is spent:

      • on each story (and compare to estimated time)
      • by developer/project
      • etc...

      Does anyone have a pointer to a solution?


      Cheers,
      Ed 

      1. If you navigate to any project > click on Summary > from the Reports link, you can select several different time tracking reports. You can choose fix versions, sometimes a specific filter that allows you to combine cross-project issues, not choose any to get all projects and select a group; anyway, I've found the various reports quite helpful to get what I need.  Just play around with them to see the results and also the details when you export to Excel.

         

         

        1. I'll have to retract my statement.  Previously, these reports were free; however, they recently made the reporting a paid plugin and, now, the out-of-the-box reporting is quite limited and not very value-add, which IMHO, makes the feature non-value-add.

           

    2. When you search issues (standard search screen) you can change the columns displayed to include the time worked.  Then you can do your time reporting however you like.  It doesn't do rollups, but you could export to excel (show view excel / csv) and roll up that way.

      This isn't a built in solution, but at least it provides some relief to the minimal out of the box time tracking.  There are also several licensed (purchased) time reporting plug ins available.

  5. Is there any way to enable 7 day work weeks for one project without affecting the global settings?  Like many companies, we run multiple project teams from a single JIRA installation.  Some teams work 5 day schedules while others are on 7 day schedules.  

     

  6. Let's be honest - the time tracking functionality in JIRA is rudimentary to say the least. I expect / hope that they'll improve it in future releases.

  7. Hi Team,

    I am not getting an option "Legacy Mode" in the the Time Tracking .Presently i am using version Atlassian JIRA (v4.1.1#522).

    Can anybody help me out.

    Thanks

    Raghuveer

  8. If i enter the time spent (effort) after confirming the issue, the original estimate is becoming 0. Is this a known issue?

  9. Hi,

    My team currently has time tracking enabled, but what I'd like to be able to do is have a gadget on my dashboard that will allow me to view the summed estimated time of each of my devs.

    Please let me know if there is something I can do to get this view.

    Thanks!

    1. TTB Widget...

      https://plugins.atlassian.com/plugins/com.ja.jira.plugin.ttb/version/2039

      ...does exactly what you are asking for.  You get quite a bit of reporting so you'll need to know that the report you want is the "period user detail" report.

       

  10. Anonymous

    6 working days per week  is not working. 

  11. How can I prevent users from logging time on a parent issue? I only want time logged to sub-tasks, so I do not want the log work dialog available on parent issues. I'd also like to make GH respect this behavior.

    1. Hi Paul,

      If you have distinct workflows set up for your issues (i.e.: one for stories and other for sub-tasks), you can configure the parent workflow, in this case the story workflow, and set the property as follows [jira.permission.work.denied] in every workflow transition. This will prevent users to log their work on parent issues.

      Last month I had the same need.

      Hope it helps you!

      Cheers! ;D

      1. I meant to say, Thank You, for this Michel. Perfect solution.

        1. Hey Paul, be my guest!

          Have a great great 2014! ;D

  12. What are the effects of changing the hours/day in the middle of a sprint?

    Can I change things back?  We want to more accurately track the available hours a developer has per day, but I'm not sure of the repercussions.

     

    Thanks,

    newbie JIRA Admin

  13. When the value of "Time Spent" entered is more than one day or even one week, for example 16 hour or 80 hour, in "Log Work", it displays awkward number of hours in the "Time Sheet Report", Sep. 24 has 16 hours a day or Sep. 25 has 80 hours a day in the previous example, even though we've configured 8 hours a day, 5 days a week

  14. Is there any way to report on the text entered in the Work Description field?  I can't find anything that will do this.

  15. we are a small team with 1 full-time developer and 1 part-time q&a engineer. since the q&a can spend 6 hours per day but the developer spends 8 hours per day it's hard to plan the resources. is it possible to assign default hours per day by issue type or by an assignee?

    1. Hi Andrey,

      My advice is to consider one of the ADD-ONs below:

      Tempo or
      Timeline
      Using one of these 2 ADD-ONs, you can control your issues or even time, whatever form you need.

      By using default JIRA time tracking, you can only set an amount of hours per issue and, after that, set worklog against the issues.

      Hope it helps! ;D

      Best,

      Michel

       

      1. got it. thank you for the suggestion, Michael Barros.

        1. Hey Andrey, you are welcome! ;D

          If you need any help, even with other stuff, just call.

          Best,

          Michel

  16. Is there a way for me to track two separate work logs on a single task?  We want the engineers to be able to estimate and log their time on a task, and QA to be able to do the same on the same task so that our estimates and burn down chart is more accurate. Currently we create a separate “testing task” for every regular task we create just to be a bucket for our QA time and estimates. This is very clunky and time consuming. Is there a better way to do this in Jira, maybe with a plug in? 

    1. Interested in others' take on this. Good question. We, too, currently use a separate Subtask for each individual working on a (parent) issue. The Subtask is assigned to a resource and an original estimate created for both. There may be a Dev subtask, a QA subtask, and a Promote/deploy subtask. Each resource logs time against their subtask and adjusts Time Remaining accordingly. I prefer this method because we can measure and reflect on the three chunks of work separately, looking at things like orig estimate vs. actuals and understanding time remaining better.

      However, often times we (my leads) get lazy and simply share a Subtask between the three of them (given my example above). They all log time against the same task and move it across the Agile board from left to right, changing assignee as needed. If the original estimate in this example does not take into account the dev, QA, and deploy efforts, then yes, our numbers are bad.