essential functionality only workaround is to manually go round tickets collating subtasks and this is a waste of my time on this planet..

Ditto. This is essential functionality.

This has been a request for years now. It would be simple to add this option. Get off you hinney and get it in there already! ... cripes

Is this still under consideration? Looks like it has been hanging out there for a while.

When creating a report of work done, it is sometimes useful to include the sub-tasks as well.
For instance, the main task may cover a UI redesign, the sub-tasks may detail each screen. When the build is done, not all screens are converted, however it would be useful to test the ones that are, and hence to include these in a report.
... or are you saying each sub-task in this case should really be a main item in its own right, despite the fact they are all closely related.

I'm not sure what others are looking for, but my reason for researching this issue was because we don't put estimates on our stories, just on the tasks and we rely on the roll-up. On certain screens, like the Sprint Report, the rollup number isn't used. If there is a different ticket for that, it would be nice to know before I end up creating one.

Ok so the completed sub-tasks will not be shown in the report.

I will update our MD for comment.

Regards,

Brett

Yeah, I think so. This isn't currently possible and we don't currently have any plans to change the behaviour.

Thanks,
Shaun

Are we going round in circles here?

I would like the sprint report to show ALL work done i.e. ALL types of issues completed.

Is this possible currently and/or is it going to be developed?

Regards,

Brett

Hi brett willson,

As I said this information is shown on the burndown chart not the sprint report?

The Sprint Report is used to show the user deliverable value delivered.

Thanks,
Shaun

Thanks for your reply Shaun.

The work does show but it is linked to the parent issue by way of time logged - the child issue (sub-task) is not shown in the sprint report under its own.

Surely the report should show each issue type completed?

Practical example:

• I have a parent issue (story/task whatever) and I want to assign 4 child issues to it.
• Lets say I estimate that the parent issue (1d) and all the child issues (1d each) will take a total of 5 days to complete.
• During the sprint, I log work of 1d against the parent issue and complete 2 child issues (1d each i.e. 2d)and complete the sprint
• The sprint reports only shows the original estimate of 1d for the parent issue and does not show the work done on the child issues or the work done on the parent issue

Please can you tell me how to get this information as it is really required.

Regards,

Brett

Hi brett willson,

The work on the sub tasks will show in the burn down chart (if you have configured your board for Time Tracking). The Sprint Report is intended to report on high level delivered value (i.e. user stories).

Thanks,
Shaun

I have been through your support process and was linked to this issue to vote and comment on.

Currently, Jira only shows the full tasks that are completed. If 4 sub-tasks have been completed no mention is made of this?

Please can you show the completed sub-tasks completed on the Sprint report as surely it is logical to report on all work done in a Sprint?

Please can you come back with a comment as this is a bit of a deal breaker for us.

Regards,

Brett

"Hi Brett,
Thanks for clarifying that with me
I did some digging, and found a feature request that talked about this : GHS-5462.
For now, I would recommend that you :
Vote, so that it will receive more attention
Watch it, so that you will receive any and all updates
Comment, and give your opinion on the matter
Please note that the implementation of new features and improvement requests falls under Atlassian's Implementation of New Features Policy.
Cheers,
Joe"

Shaun/Anyone,

Is there any update regarding this request?

Thank you.

Dean

Shaun,

The reason for this request is because we would like to run Sprints based on Users, not just tasks in a project. We have numerous projects and a couple of different rapid boards, but because of the many tasks (in general) we have, we don't have any 1 person work on a single project, they work on numerous tasks and projects at once. We decided to try out Greenhopper Sprints on User accounts, instead of by Projects. A single user works on tasks across multiple Projects, so we'd like to track work on a User and not on a Project. When a user completes any work and we close out a weekly Sprint, we'd like to see what they completed, tasks and subtasks. Because they don't work on just primary tasks only, they can complete numerous subtasks, but the Sprints don't show anything, neither do the Sprint Reports.

All in all, we'd like to see what a user actually completes even if it is subtasks.

...This is the reason for our request and I really REALLY hope you guys implement it, especially since you have seen this requested a few times prior...

Thanks.

Dean Berman

Hi Arthur,

This has been requested a few times, but I'm not sure of the exact reason this is desired. The stories represent the actual deliverable, the tasks are usually just technical steps to get there. Most people will not be interested in those technical steps (and GreenHopper will not allow a story to be completed in a Sprint if its tasks are not completed).

So we don't have any plans to implement this, but it would be helpful to get further feedback about the reason the customer is looking for this and how their process makes this important.

Thanks,
Shaun