How to add sub-task commit hours and completed hours to parent activity in sprint report

[Keith]

I want to generate sprint report, but the estimated hours and logged hours in sub-task in not added to parent activity. As a result, the commited hour and completed hour in report is 0.

How to config to make it, thanks in advance.

[Danut M _StonikByte_ · Accepted solution]

Hi @Keith,

Try our Great Gadgets app. It offers all you need for tracking your Scrum (and Kanban) projects by time estimates and can include the subtasks in the calculation.

For example, by using the Sprint Burnup Burdown Chart gadget you can generate the sprint burndown based on time remaining and time spent (logged hours).

And, on its Data tab,  you can visualize the sprint report, which includes the subtasks. This report can be easily exported in CSV.

Similar to this, the app offers Team Velocity and Release Burnup Burndown Chart. Both offers support for time estimates and subtasks. 

Take a look over this article from our blog to make a better idea:  Tracking an agile project that uses time estimates with Great Gadgets for Jira 

Hope this helps. If you have any questions, please don't hesitate to contact us at support@stonikbyte.com. This app can be a great asset for your team and company.

Danut.

[Keith]

Hi @Danut M _StonikByte_ ,

I'm not sure which app to download, it seems all are not applicable for me. The jira project url is: https://jira.tools.sap/projects/XXX?selectedItem=com.atlassian.jira.jira-projects-plugin:report-page

Any advice for it.

Keith

[Danut M _StonikByte_]

Hi @Keith,

In this case I think is best to ask your Jira admin to install the app. You will not be able to install it by yourself if you are not a Jira admin. 

Hope this helps. 

Danut.

[Linh Pham_Ricksoft_Inc · Accepted solution]

Hi @Keith , welcome to the community!

Unfortunately, in the sprint report, you can only track work based on standard issue types (Story) and not subtasks. There's an existing feature request here: https://jira.atlassian.com/browse/JSWCLOUD-5462

Perhaps you can consider pulling the sprint overview from filters? In my team, we mainly rely on JQL to generate these insights: