Why Jira thinks there's no time left when there's still estimation time

[andrewsharapoff]

Summary

Hi! As a Project manager on one of products, I have spotted an issue, when Jira thinks that there's no time left for the task but according to the estimation it's at least a third of it

Here's more clear specs:

1. Application: Jira software
2. Project type: Software
3. Managing type: company managed
4. Sprints: enabled
5. Advanced roadmaps: in use
6. Estimation type: original time estimate

Ticket info:

1. Ticket type: bug
2. Start date: 15 Nov 2023
3. Estimation: 8 hours
4. Time left: 3.67 hours
5. Jira's value: 100%, 0 of 3.67 hours remaining
6. Current state date: 16 Nov 2023

Some screenshots

Question:

Having checked all the values that affect the estimation and timeline, either what am I missing or does Jira really has an issue with placing tickets on a timeline?

Thanks in advance!

[Pablo Brincat]

Hi Andrew,

The issue you’re encountering in Jira, where it shows no time left for a task despite there still being hours remaining in the estimation, can be a bit puzzling. Let’s break down the possible causes and solutions:

Understanding the Estimation and Tracking System in Jira

Jira calculates remaining time based on the original estimate and the work logged against the issue. Here are a few things to consider:

1. Time Tracking: Check how time tracking is configured in your Jira instance. Jira’s time tracking calculates the remaining time as Original Estimate - Time Logged. If someone logged more time than the original estimate, it could lead to showing 0 hours remaining.

2. Work Log Entries: Review the work log entries for the ticket. It’s possible that the total logged time has exceeded the original estimate, which might not be immediately obvious.

3. Configuration of Time Tracking: Jira allows for different configurations of how time tracking works, including how it calculates the remaining estimate. Ensure that your Jira configuration aligns with your project’s needs.

4. Advanced Roadmaps: Since you’re using Advanced Roadmaps, check if the issue might be related to how Advanced Roadmaps interprets or displays this data. Sometimes, plugins or extensions interpret data differently than Jira’s core functionality.

Potential Causes and Solutions

1. Over-Logging of Time: If more time was logged than was originally estimated, Jira might show 0 hours remaining. This could be a simple case of over-logging.

2. Misconfiguration: Ensure that the time tracking settings in Jira are correctly configured. This includes checking the time format (hours/minutes) and how the remaining time is calculated.

3. Jira Bug: While less likely, there’s always a possibility of a bug in the software itself. If you suspect this, checking Atlassian’s support forums and contacting their support might be necessary.

4. User Error: Sometimes, it’s a matter of user error in logging work or setting estimates. A review of the process with the team might be helpful.

Next Steps

• Review Time Logs: Look closely at the work logs on the ticket. Ensure that the total time logged is as expected.
• Check Configuration: Review your Jira time tracking and Advanced Roadmaps configurations.
• Consult Jira Documentation/Support: If the issue persists, consult the Jira documentation or reach out to Atlassian Support for guidance.
• Team Training: If the issue is due to user error, some additional training or clarification with your team on how to log time and estimate tasks in Jira might be needed.

It’s great that you’re keeping a close eye on these details in your project management. Tracking down issues like this can be key to maintaining accurate project timelines and forecasts. If you have any more details or specific questions, feel free to share! 🚀💼🔍

[Walter Buggenhout]

Hi @andrewsharapoff,

Advanced Roadmaps looks at the remaining estimate to track progress and is not aware of the value in the original estimate field.

While usually the original estimate is copied over nicely into the remaining estimate field initially, I don't see any remaining estimate value in your screenshot. It does sometimes happen that this field is not correctly set or updated when tracking work. My guess is that the cause of your issue is related to that somehow. See if you can correct the remaining estimate of your issue to 4.63h and make sure that this is correctly updated also when people track additional time against the issue.

Hope this helps!