Logging time on issues

Jira Software provides the flexibility to set your estimation and tracking statistics differently, depending on your team's needs. Time tracking features project schedule planning and time expectations management. Thanks to its reports, you can see the original and current time estimates for all the issues, and whether they are ahead or behind the original schedule.

Product teams often need to be able to estimate how long a product will take to deliver from sprint to sprint. As they work through the stories, the team will develop a cadence of completing <x> units of work they had estimated. This is also called velocity. The team has to track the amount of estimation units they've completed from sprint to sprint to know how much they can fit into each future sprint, and have conviction that all the work will be completed.

You can monitor the tracking time info by just watching the issue time tracking color bars.

Here's how time tracking appears on an issue:

  1. Time tracking panel: Shows the time logged so far, and time remaining. Click anywhere on the panel to log time.

Before you begin

Make sure that your Jira admin has enabled time tracking, and that you have the Work on Issues, Delete Work Logs, and Edit Work Logs project permissions. Anyone with the Browse Project permission can view time tracking info on an issue.

tip/resting Created with Sketch.

We're rolling out a new issue view, with a consistent appearance across Jira and one screen to view and edit. It looks a little different and some procedures have changed slightly, so take a look at our updates page to see what's changed and get the latest updates and Work in the new issue view for info on how to complete common tasks. To turn the new issue view on or off in Jira Software and Jira Core for now, head to Your profile and settings () > Personal settings and toggle the switch for the New Jira issue view.

The new issue view is permanently on for all business boards and next-gen software projects.

If you don't see the Personal settings option when you click your avatar, the switch to turn the new issue view on or off will appear under Profile.


Estimate an issue

Before you start work on an issue, you can set a time or other type of estimate to calculate how much work you believe it'll take to resolve it. The field you set your estimate in depends on what's chosen as your estimation method. This'll be set to story points (where you only estimate story and epic issue types), time estimate, issue count, or another custom method.

To set an estimate for an issue:

  1. Select the issue and choose the Story pointsTime estimate, or custom estimation field.
  2. Enter the number of story points or amount of time you believe it'll take to complete work on the issue.

Example of story point estimation

  1. Selected issue: Choose an issue to see its details on the right side.
  2. Estimation field: Enter Story points or Time estimate depending on your estimation statistic.

tip/resting Created with Sketch.

You can enter time estimates and log time in weeks (w), days (d), hours (h), and minutes (m). For example, you could estimate 3w or 2d 4h 30m.

Log time on an issue

Once you've started to work on a specific issue, log time to keep a record of it. That'll let you to your original estimate with how long it actually took to resolve the issue.

  1. Open the issue and select ••• > Log time (or click on the time tracking field)
  2. Fill in the Log time fields and select Save


Items below this point aren't available in the new issue view just yet. Click the issue key to open the full-page view to perform these actions.


You can also log time when you resolve or close an issue by editing the log time fields.

Edit a time log entry

You can can edit your own time log entries if you've been granted the edit own work logs permission. You can also edit other people's time log entries if you've been granted the Edit All Work Logs permission.

  1. Open an issue, choose Comments, then choose Work log.
  2. Find the time log entry and choose Edit.
  3. Complete any relevant fields and choose Save.


tip/resting Created with Sketch.

Editing and deleting work log entries is coming soon to the new issue view. Until we release it, you'll need to click through to the old view to edit or delete entries.

Delete a time log entry

You can delete your own time log entries if you have been granted the Delete Own Work Logs permission. You can also delete other people's time log entries if you've been granted the Delete All Work Logs permission.

  1. Open an issue, choose Comments, then choose Work log.
  2. Find the time log entry and choose Delete.

You'll be asked whether you'd like to adjust the remaining time estimate. If you choose to adjust it, you can let Jira automatically adjust the time remaining by adding back the deleted time, or set it to another time manually.

Customized Jira sites

Jira applications can be customized by your Jira administrator by adding the log time and time tracking fields to the customized screens. This way, you can log time and specify time estimates on the same Jira screen when performing any Jira operation, like editing, creating an issue, or transitioning an issue to another status.

To work or specify time estimates on the same Jira screen:

  1. Navigate to the issue and view its details.
  2. Perform the customized Jira operation that allows you to log time and specify time estimates on the same Jira screen. For example, assuming that your Jira admin has added the time tracking fields to the Resolve Issue Screen and this screen also retains the default Log time fields, select Workflow > Resolve Issue at the top of the issue.


If your Jira admin has configured the Log time fields as optional, you can choose whether or not to log time by checking the Log time checkbox.

If your Jira administrator has made logging time mandatory, you won't see the Log time checkbox. You'll instead need to log time when transitioning an issue.

Last modified on Mar 20, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.