Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,365,056
Community Members
 
Community Events
168
Community Groups

Remaining time estimate in burndown report is not being recorded while sprint was created

Hi, I have some issue related to Remaining time estimate.

1. The sprint has been created by some user.
2. The sprint contains defects and stories
3. Remaining time estimate has been provided in sub-tasks during issue creation, which is visible in parent issue's time tracking. (If we remove Include sub-tasks, the Time tracking data will be invisible because it was coming from child tasks).
4. I added few details in active sprint's backlog, to view time estimates (i.e., Σ Original Estimate and Σ Remaining Estimate). So I can view total time estimate and total remaining time. So data is fine here. (shown in screenshot attached)
5. When I check workload by assignee in sprint's backlog (by pressing three dots), I see Remaining estimate and Remaining time estimate based on assignee. Which is zero in all cases... The workload feature addition details provided by Atlassian is here. https://jira.atlassian.com/browse/JSWSERVER-11177?error=login_required&error_description=Login+required&state=cd4a5d3e-674a-4ab9-9569-e0d09497f9d4
6. This Remaining Time estimate is zero for all the issues where time is being taken down from sub-tasks, while it is giving value for those were estimate time has been added for parent task. (shown in screenshot attached)

7. When I see burn down report for that sprint, it takes the same figures (as in assignee workload) .Why Remaining time estimate is not being read properly when Σ Remaining Estimate  per issue is present? (shown in screenshot attached)

***********************************************************************************

It is the case that sprint does not take sub-task's time estimate when sprint is created?Because when sub-tasks are showing correct estimate after work-logs are added in later point of time, why the same remaining estimate is being recorded in burndown when sprint was first created? (shown in screenshot attached)

Please provide your opinion based on your work exp.RemainingEstimate.PNGBacklogConfig.PNGWorkloadBYAssignee.PNG

Thanks

1 answer

1 accepted

0 votes
Answer accepted

My issue is resolved.

The sprint filtered only parent issue, sub-tasks were not included in filter, that is why remaining time estimate was not recorded.

How do you get time (and total of sub tasks) from sub-tasks to be visible into Parent issue? This is not yet working in JIRA.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events