This is with reference issue#260
Thanks for your quick response. I see the grouping options are given already. But Summary Tab is unique and was very helpful. It gives us the insights about the total worklog of user as well as the Project in one single view in horizontal and vertical ways.
In grouping option, for example if I group by Project, I will get a worklog Project wise only. If I need to check for one user, I need to again switch the grouping. In Summary tab, As everything was in single wise, it helps us to create a report and submit it to our Management.
Grouped Option :
Worklog Option (Here it more readable as it is horizontal and vertical manner) :
Also, the old worklog will get removed and it will be there always?
Hi @SelvalakshmiPraveen - Thank you for your detailed response. I get your point. I will try to provide that option max by this month end within new report.
And to answer your second question, Yes, old worklog report would be gone, but will first hide it and only after I ensure no users are missing some functionality from it, I would completely remove it. That would take few months before it is completely removed. I would first add a message well in advance before I hide it and then would remove it later, waiting enough to address any queries I receive from users.
Thanks for taking up adding Summary tab as an enhancement.
Hi @SelvalakshmiPraveen - This implementation has been done for Date range based report with no custom grouping used. This change is now available in Web version already and in next couple for days this would be published for extension users.
But for sprint based report and when custom grouping is used, this tab would be hidden as that needs more effort and would be added later this quarter.
However, all the functionality available in old worklog report is now available in new report as well. Hence I consider this issue as resolved, but still will have this ticket open until the change is implemented for sprint report.
Thanks for adding this feature back.
As the initial ask is resolved, closing this ticket. Any improvement would be considered based on future use cases.