While exploring the use of the new Jira issue view on classic projects, I could not track down a way to incorporate the Remaining Estimate on subtasks and the three summed time tracking fields (estimated, remaining, and logged) on Stories/Bugs for use in this view. How can these be incorporated in the new issue view?
Use case below
Under the old issue view:
Story and Bugs have story points but no specific time estimates values. Time estimates are tracked at the subtask level. Each subtask has an Original Estimate and Remaining Estimate value. In the story/bug time tracking section, there is an accurate sum of all the Estimated, Remaining, and Logged time for all of the subtasks under it.
In the new issue view:
The same story shows a time estimate of 0m and no time tracking logged. On the subtasks, the Time Estimate reflect the original time estimate for that specific task and the Time tracking compares logged time versus the time estimate. If I switch back to the old view on this subtask, only the Original Estimate and Logged time have values.
How have others addressed this type of scenario when going to the new view?
I have the same problem and have had to revert to the old view.
This is not good at all as I've been writing the documentation for the project using the new view, since it will no doubt be forced on us in the near future. Just like the Confluence Documentation Theme was, even though users complained bitterly all through the "beta" use of it.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events