-
Bug
-
Resolution: Tracked Elsewhere
-
Medium
-
38
-
Severity 2 - Major
-
17
-
Issue Summary
In the board view, when clicking upon a card(which is a parent), the sub-task time tracking original estimation is not summed up to its parent time tracking original estimation field within the New JIRA Issue View.
The same applies when we directly access the issue (card).
However, when clicking on a card in the board (in old view), it opens a pop up box on the right which shows the time estimation for both parent and subtasks.
New issue view
Board click on card :
Parent issue view :
Subtask:
However, in the old view, it does show the sum value of the original estimation in parents and in sub-tasks.
Old issue view
Board click on card :
Parent
Subtasks:
Steps to Reproduce
1. Go to board settings > Estimations
2. Set the estimation statistics to Original Time Estimate
3. Under Time tracking, choose Jira's Remaining Estimate and Time Spent fields.
4. Now create an issue and add the original time estimate
5. Within the issue, create a subtask and add the original time estimate as well
Example :
- When an issue has 100m set in time tracking.
- For the subtask of that issue, it is also set for 100m.
- When viewing the issue in backlog and active sprint boards.
- The expected value for the time tracking should equal to 200m
- However, it only shows the parent issue which is 100m
Expected Result:
The parent task should have the sum of the Original Time Estimate of the current issue and the subtasks.
Actual Result:
The parent task only shows its original time estimate and not including the sum of the subtasks.
Workaround:
You can choose from either option:
1. Turn off the New JIRA Issue View.
2. View the time estimation from the board itself where it shows the time estimate in the cards
3. Use filter navigator where you can add the column (Original time estimate) to view the total time estimation for the issue
Update as at 8th Jan 2020
This issue is related to the subtask JRACLOUD-70150 , you can use the workaround mentioned here but for the long term fix , please also see the subtask above.
- is related to
-
JRACLOUD-70347 Time tracking widget missing in the new issue view
-
- Closed
-
- relates to
-
JRACLOUD-70150 Sub-tasks no longer have their time tracked on the parent issue for the new Full View Issue experience
- Gathering Interest
[JRACLOUD-69587] New JIRA Issue View don't roll up the time tracking of subtasks to its parent from the board view
We started to roll out Azure Devops to manage our projects. We grew tired of waiting for Atlassian to take care of the numerous bugs on its platform.
The issue described here is not only an inconvenience. It's a loss of productivity for our teams, which translate to a loss of money. This has a financial impact on our projects.
Hi, it seems like this issue is not resolved even though the status is now 'closed'. Do you have any plan to truly fix it ? It is a huge inconvenience.
Now that we cannot switch the New Jira view back, is this issue prioritized to be fixed?
Dear Atlassian team,
I understand that in your point of view this is a medium priority issue. However, it's a really important feature to development lifecycle and teams who need to have proper view of original estimate x time tracking - this really impacts my company's life and is critical for us.
I can see many watchers in the issue, all those people are waiting for this resolution, therefore could you please prioritize the resolution of this issue?
Regards,
Renata Bianchi
The 'Old View' also has an issue in terms of calculating the correct values for Estimated, Remaining and Logged hours. Below is an example to illustrate this -
(Refer to ticket https://digicomm.jira.com/browse/NCE-1270 and compare Old and New views)
The estimated hours in the 'New View' was entered as "18h", however, estimated hours in the 'Old View' incorrectly displays 1d 2h (i.e. 26h).
Moreover, Logged + Remaining doesn't add upto Estimated.
Logged + Remaining = 28h ; Estimated = 26h
Is this a known issue and ticket raised for this as well? Is there a workaround to get the correct values to display?
Dear watchers,
We have reviewed this bug from a current standpoint and we understand that this issue is a pain-point for many of you. We have since improved both the description and the workaround. This should help and also note that the next steps will be updated within the next few months based on the update provided at the related ticket here: JRACLOUD-70150.
If you need any assistance at all with the workaround, please feel free to raise a new Support Ticket and we will help you better from there. Feel free to pass any updates needed here. If you have any further questions let us know as well, we'll be happy to assist you.
Kind Regards,
Ku Ahmad Najmi Ku Jaafar
Atlassian Cloud Support
We moved all of our time reporting into Power BI. There are a few Power BI connectors on the marketplace. In the end we have found that to be a very good solution. While it was a significant investment to set up, we have found it to be very worthwhile. The flexibility of the reporting we are able to do is fantastic compared to any project management software I have used.