Can I check Story points from subtask?

[조성진_상연_]

I've assigned many subtasks

and I want to check each story-points

I know I can move to story from each subtask, then check story-point

but Is there any way to see all at once?

In my case, subtask does not have story-points from parent(Story), so I have to check points at Story issue.

[Earl McCutcheon]

Hello @조성진_상연_ ,

Story point estimation is a method of planning the effort needed to complete a task at the project level, then comparing that estimate to the actual work logged after the completion to see if the estimate was accurate to prepare for the next planning session to help better understand a project's velocity, and the story points should not be used as a basis to estimate time available after the start of a sprint on an individual issue level as the estimation is in general weighted against the project total not just the individual issue.

The agile coach tutorial "Working with issues in Jira Software"  gives some really good insight on this noting:

In traditional development teams, managers would estimate items in 'man hours'. They could then count up the hours in the backlog, divide by the number of people on the team and hours in the week to reach a forecast date. Of course, these estimates often proved to be wildly inaccurate because they didn't take into account the natural estimation characteristics of the team (for over/under estimation), unexpected interruptions or the development of team performance over time.

So in the Scrum world, most teams don't try to achieve estimation accuracy; instead they aim to achieve a reliable velocity. Velocity is a measure of the number of estimation units that a team tends to complete from sprint to sprint. After their first few sprints, most teams will achieve a reasonably consistent velocity. Armed with velocity and estimates on backlog issues, teams can predict how long portions of the backlog will take to complete.

So realistically by design the overview of estimation should be done project managers based on input from the team but not used as a metric by the team to judge what work effort should be given to an issue.

And the following thread discusses this even further:

• https://community.atlassian.com/t5/Jira-questions/How-can-I-check-the-individual-velocity/qaq-p/37221

however, if you did want to build out a report on story points of issues you are assigned to and you want to see the individual burn down, you could create a board with your own saved filter that included "assignee = your user name" and all other conditions to the existing board filter your sprint is included in that you need, and it will show your individual burndown chart including story points.  I would also recommend not to do this though as burndown is meant for teams, and the focus of team members has to be to make the team burn down to reach its targets.

Another option would be to export the issue details to a spreadsheet and build out a custom report on your issues using something like Jira Cloud for Google Sheets (Official) or Jira Cloud for Excel (official)

Regards,
Earl

[조성진_상연_]

Thanks for your detailed answer, I can even more understand the story points.

 included "assignee = your user name" and all other conditions to the existing board filter

But the problem is that I'm not assignee to story, I'm just assignee to subtask in the story

[Earl McCutcheon]

Hello @조성진_상연_ ,

For a filter to get the parent issue will need to look into either exporting the data to the external spreadsheet application I noted previously to parse out the content accordingly in the external tool or look at a third part add-on app to extend the native JQL options. 

One third party app that I know can do this is ScriptRunner and there is an example on the JQL available with this tool in the following thread:

• https://community.atlassian.com/t5/Jira-questions/Searching-for-all-subtasks-assigned-to-me-and-their-parent-Jiras/qaq-p/1057900

Regards,
Earl

[조성진_상연_]

@Earl McCutcheon Thanks for your suggestion.

[elizabeth_jones]

Have you tried the issue navigator to visualize those subtasks and their associated story points? 

[조성진_상연_]

Hi, I don't know the issue navigator, do you mean issue filter?