Sum of the Story Points of Stories and Tasks for all Epics (1k)

[Sonia Goławska]

Hi there,

I recently asked a question, whether lookup is an applicable solution for custom fields and received info from @Bill Sheboy (thank you for that!), that it's better to copy data from custom field to Story Points and then use lookup. I did this, I managed to copy and paste value from custom field to Story Points, however I stuck on lookup. It reverts wrong value. There are different Epics linked to each other (scope of the project is vast), so perhaps it has an impact (?) You can find below the automation rule, I did the same for both stories and tasks with different variations - together, separately etc.

My intention - to sum up Story Points of all stories and tasks under each Epic and present value within the Epic itself - for all the Epics in the Project (around 1K Epics).

I use Jira Cloud. 

[Fabian Lim]

Hi @Sonia Goławska

Take a look at this post: https://community.atlassian.com/t5/Automation-discussions/Jira-Automation-Complete-Video-Guides-on-how-to-Sum-Up-Story/td-p/1741948

It has several rules that you can use to sum up the story points at the epic level.

[Sonia Goławska]

Hi @Fabian Lim, thank you - that exact tutorial I've already used to build current rule (in the screenshot), which unfortunately reverts wrong value.

[Bill Sheboy]

Hi @Sonia Goławska 

I do not believe that is possible with an automation rule, as there is a processing limit of 100 issues for triggers, branches, lookups, etc.

The only built-in work-arounds I can think of are:

• Use a scheduled rule on JQL for epics which do not have story points set, and the rule will process them 100 at a time.  Run the rule more frequently until it catches up to sum for all epics.
• Figure out a way to partition your issues using something which groups them into smaller chunks, and then sum values across those first. (e.g. component, label, some text in the summary, etc.)  And then add up the chunks.

If we pause for a minute to consider the problem you are trying to solve, what will you do with that total number of story points?  Perhaps the same result could be achieved by using built-in reports/gadgets on the epic.

Kind regards,
Bill

[Sonia Goławska]

Hi @Bill Sheboy

Do you think this kind of action can be done via REST API? Are there also some kind of limitations as in automations rule for lookups etc? Moreover, is it possible to use JavaScript to perform additional operations on data?

The main purpose of those story points is to create a high level timeline, so it will give us an idea of how much time this project requires (more or less).

[Bill Sheboy]

The REST API also has an issue limit, so you would need to page through the results when there are more than 100 issues assigned to an epic.

As I noted above, if you have lots of epics and they each have fewer than 100 child issues each, you could use two rules: a scheduled rule with JQL and a rule triggered on task's story point changes to update the parent epic.  This could then run until there are no more epics without story points.  The second rule would refresh after changes. For example the scheduled rule could be:

• trigger: scheduled with JQL... 

project = myProject AND issueType = Epic AND status != Done AND "Story Points[Number]" IS EMPTY

• ...the rest of your rule to update the epic

By the way, I note in your Lookup Issues JQL an apparent error.  You want to match the Epic Link to the key, not the name.  So please try this inside of your branch, where {{issue}} will refer to the epic.

issueType IN ("task") AND "Epic Link" = {{issue.key}}

[Sonia Goławska]

@Domenico Corniola help me man :D