# Time spent and remaining estimate in Jira Cloud: what each field means By Sync4us · Published on 17 October 2026 · Sources reviewed on 17 October 2026 **Time spent** shows logged time. **Remaining estimate** expresses how much work is thought to be left. **Original estimate** holds the initial reference estimate. Logged hours plus remaining hours do not have to match that earlier forecast. \- The task was estimated at eight hours. \- We've logged six. \- So there are two left. \- There are five left. \- Brilliant. Do we need to learn to add up again as well? The maths works. The forecast has changed. Before booking a meeting to debate subtraction, let's see what each field tells you. ## Original estimate, time spent and remaining estimate: the differences | Field | What it means | What question it answers | |---|---|---| | **Original estimate** | Original estimate | How much did we think it would take? | | **Time spent** | Logged time | How many hours have been recorded? | | **Remaining estimate** | Remaining estimate | How much work do we think is left now? | Original estimate can be edited: its name does not guarantee that it still contains the first figure. Time spent adds up work entries, also called *worklogs*. To find their authors and dates, look at the individual entries. Remaining estimate is a forecast of work still to do. It is not a stopwatch or a delivery date. Jira lets you log work and review what is left. [Atlassian documentation](https://support.atlassian.com/jira-software-cloud/docs/log-time-on-an-issue/). Work has an annoying habit of bringing surprises without asking permission. ## Example: eight hours estimated, six logged and five remaining Imagine a fictional issue: **DEMO-42, fix a report export**. At the start, you estimate eight hours. After working and logging six, you discover another case that also needs a fix. You review the remaining work and estimate five more hours. ![Fictional example: 8 h originally estimated, 6 h logged and 5 h remaining.](https://sync4us.com/assets/resources/time-spent-remaining-estimate-jira.png) *Fictional example: six logged hours and five remaining hours give a current forecast of eleven hours. The original estimate is still eight.* | Field | Value | |---|---:| | Original estimate | 8 h | | Time spent | 6 h | | Remaining estimate | 5 h | The current total forecast would be **eleven hours of work: six logged plus five remaining**. That does not mean Original estimate has changed to eleven. In this example, it still shows eight. Nor does it mean eleven hours have already been worked. The difference may have a reasonable explanation: you now know something you did not know before. On its own, it does not prove that the worklogs are wrong. The useful question is: what changed? Tweaking figures to make them look nice again will not finish the remaining work. That's what presentation charts are for. ## What to check when logging, editing or deleting a worklog Before saving, check the duration, date and how the remaining estimate will be handled. The options you see depend on the configuration. If you edit or delete an entry, check the remaining estimate afterwards. Correcting logged hours and assessing unfinished work are different decisions. [Logging and correcting time in Jira](https://support.atlassian.com/jira-software-cloud/docs/log-time-on-an-issue/). For the steps, see how to [log time in Jira](https://sync4us.com/en/guides/log-time-in-jira) or [edit and delete a worklog](https://sync4us.com/en/guides/edit-delete-jira-worklog). ## An issue's time spent is not your timesheet for today The issue shows six logged hours. You worked two this morning. Both figures can be right. In our example, those six hours could break down like this: - Three hours you logged on Monday. - One hour someone else logged on Tuesday. - Two hours you logged today. Your entry for today would be two hours. The six hours belong to the issue as a whole. To review your day, check each entry's **author, date and duration**. This [guide to reviewing your Jira hours](https://sync4us.com/en/guides/review-jira-hours) explains the process. Copying the accumulated total can produce a wrong timesheet from perfectly valid numbers. ## What to do when the figures do not add up 1. **Open the worklogs.** Identify the person and day each entry belongs to. 2. **Look for specific errors.** Check for possible duplicates or incorrect durations. 3. **Review the remaining work.** Decide whether the estimate reflects what is left to do. 4. **Explain the difference.** Check what changed since the initial estimate. 5. **Verify the result.** Check the values after saving. The goal is for each figure to explain what it should. They do not all need to hold hands. ## Frequently asked questions about Jira estimates **Does changing Original estimate update Remaining estimate?** Not necessarily. After logging work or manually adjusting the remaining estimate, the two fields may stop staying in sync. Check both before considering the change complete. [Atlassian explanation](https://support.atlassian.com/jira/kb/time-remaining-not-updating-after-changing-original-estimate-in-jira-cloud/). **Why can I not see these fields in Jira?** Their availability and presentation depend on the configuration. Ask your Jira administrator to check time tracking and the visible fields. [Atlassian help](https://support.atlassian.com/jira-software-cloud/docs/log-time-on-an-issue/). ## Review your day without opening Jira With Sync4us, you can view your worklogs, review your day and prepare your entries without opening Jira. You review and confirm before sending them. **[Create my free account](https://sync4us.com/en/#beta)** *Free beta for Windows. Access subject to availability.* Hours get logged. Estimates get reviewed. A crystal ball is still not included. ## Sources and scope - [Log and correct time in Jira Cloud](https://support.atlassian.com/jira-software-cloud/docs/log-time-on-an-issue/) - [How original and remaining estimates relate](https://support.atlassian.com/jira/kb/time-remaining-not-updating-after-changing-original-estimate-in-jira-cloud/) A guide to Jira Cloud. Fictional example with no real personal data. Options depend on configuration and permissions.