summing up story points of subtasks with designated value of custom field using smart value

[Josh]

I tried {{issue.subtasks.Story Points.sum}} to sum up story points, and it worked.

After that, I wanted to sum up only issues with the value I want of the custom field. Field is 'Components', and it has values 'Backend', 'Frontend', 'Business', 'Design'.

I thought {{issue.subtasks.Components.Frontend.Story Points.sum}} would work, but it didn't print any text. Is there any way of using smart value to use as I intended?

[Trudy Claspill · Accepted solution]

Hello @Josh 

Welcome to the Atlassian community.

You will need to use a Lookup Issues action with a JQL statement to retrieve the subtasks that match your condition; i.e.

Component = "Frontend" and parent={{issue.key}} and issuetype in subTaskIssueTypes()

Then you can use a smart value like this to get the sum of story points in the results set.

{{lookupIssues.Story Points.sum}}

[Josh]

Thanks Trudy! It really helped me! 

[Bill Sheboy]

Hi @Josh -- Welcome to the Atlassian Community!

First thing, why do you have story points assigned at a sub-task level?  One of the ideas of story points is toward delivering value to production, and one of the ideas of sub-tasks is a piece of work contributing to a larger item, and not be individually releasable.  And so using story points for sub-tasks does not seem a good fit.  Would you please explain your usage?

In addition to Trudy's suggestion...

I see what you were trying to do with the dot-notation filtering, but the challenge is if that worked, the visible scope would reduce as you progressed, left to right, in the expression.  And so story points would not be visible "below" the level of components.

An alternative is to do this in one step using an iterator, smart value list filtering, and a math expression.  Perhaps like this:

{{#=}} 0 {{#issue.subtasks}}{{#if(equals(components,"Frontend"))}} + {{Story points|0}}{{/}}{{/}}{{/}}

Kind regards,
Bill

[Josh]

Hi Bill!

First of all, thank you for your answer! Our usage of sub-task is like other jira users, piece of work contributing to a story. The point we are using story points in sub-task is that we are focusing on tracking the velocity of our product.

We are short of time(like all other companies), and our sprint cycle is about half length than usual, to keep our tension high. And we found out story level tracking makes us hard to find out what's happening in the sprint.

I really appreciate your answer, and you and Trudy really helped me! Thanks again!

Best regards,

Josh