Roll up story points to Initiative and Theme

[Nataliya Krymska]

Currently Jira has an issue with story points roll up at Advanced Roadmap. 
All details are here: https://jira.atlassian.com/browse/JPOSERVER-2890

Im trying to find a workaround for Advanced Roadmap.

The goal is to sum up Story points from Epic to Initiatve and Themes. 

I have tried to turn off the roll up and use a formula
from this article https://confluence.atlassian.com/automationkb/automation-for-jira-how-to-create-a-rule-that-sums-up-the-story-points-from-epics-to-a-linked-initiative-1188761726.html (and similar)

but it doesnt work for me. 

Any advice how to calculate story points for high level issues (Themes and initiatives) and keep Advanced Roadmap? 

Thank you in advance. 

[Trudy Claspill · Accepted solution]

Hello @Nataliya Krymska 

Welcome to the Atlassian community.

The article you referenced is for Jira Server/Data Center, as noted at the top of the article. Jira Server/Data Center automation does not have all the same functionality that is available in Jira Cloud, so the solution is different.

Take a look at my answer on this post. It is about summing up the Original Estimate, but the concept and structure are the same for Story points.

[Nataliya Krymska]

Hi @Trudy Claspill 
Thank you a lot for your advice. 
I tried similar, but still no results. 

This is a snapshot of formula:

 

Here is a set up shows that Parent Link is not empty: 

Audit log: 

[Trudy Claspill]

According to the log the rule was triggered for issue NKT-5, and that issue failed to meet the first condition - issue type = Epic. Therefore the rule did not proceed.

If the summaries shown for the issues in your other image are accurately noting the summary type, the NKT-5 is a Story type of issue. The only issue from that image that is both an Epic and has a Parent Link value is NKT-2.

[Nataliya Krymska]

@Trudy Claspill  correct. 
I changed story points for NKT-5, it is story. 
And I also have automation for Epic sp summ up.

Changing the "Story Points" field for NKT-5, triggers rule for Epic and changes "Story Points" at Epic, NKT-2.
Which should trigger the rule for Initiative. 

Is it correct? 

Expectation is to have 5 story points for Initiative, because Epic received 5 story points (based on automation)

[Trudy Claspill]

On the Rule Details page for the rule there is a checkbox labeled:

"Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule."

You need to have that box checked to enable the rule to run when the Epic's story points value has been changed by the execution of a rule, which is the scenario you describe. Then, if you change the points for NKT-5 you should see an execution triggered by NKT-5 which will show the "condition failed" message, and a separate execution for NKT-2 which should proceed to run.

[Nataliya Krymska]

oh, great!

Yes, now rules start to communicate :)

You're right, it shows "failed"

Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Story Points (customfield_10023) No fields or field values to edit for issues (could be due to some field values not existing in a given project): NKT-1

May I kindly ask your advice here as well? Am I right to assume I need to change configuration for "Story points" field somewhere?

[Trudy Claspill]

Do you have the Story points field in the Field Configuration and on the screens used for the Initiative issue type?

[Nataliya Krymska]

@Trudy Claspill 
looks like everything is configured properly.
But ..maybe I missed smth? 
. 
1) Fields. "Story points" field is present 

2. Screens. 
Could you please advice how can I check the Screen configuration properly and make sure "Story points" is in place? 

Thanks 

[Trudy Claspill]

You can find Screen information under Project Settings > Issues > Screens. 

Also check for the field under Project Settings > Issues > Layout.

[Nataliya Krymska]

hey @Trudy Claspill 
Im afraid Im going to ask your help here as well

We checked all parameters, and it looks like we have "Story points" field activated everywhere. 

But it still doesnt work. 
What we missed? 

[Trudy Claspill]

I missed mentioning another place to check. You will need to check the Context for the Story Points custom field. You can check that from Jira Settings > Issues > Custom Fields.

Search for the Story Points field and click on the # context link.

That will give you a screen similar to this.

You may see multiple configuration schemes listed there. Click the Create, edit or delete contexts link.

Check if the Initiative issue type has been included in the Story Points field context for the Default Configuration Scheme. If it has not you will need to edit the context configuration and add it.

[Nataliya Krymska]

Hey @Trudy Claspill 
Thank you for advice, now its configured :) 
And formula is executing :) 

According to automation log field should be updated. 
But for some reason it doesnt update the field with expected number. It updates it to "None"

May I kindly ask your advice here as well? 

[Trudy Claspill]

Hello @Nataliya Krymska 

I have set up the same rule in a test project, and it works for me.

Can you show us the details of the Edit Issue step, so I can check it for any potential typos?

Sometimes Automation Rules can get glitchy if they have been edited a lot. If there are no typos in the Edit Issue step, that I suggest that you try making the rule again from scratch? Disable this first version, make a new rule with the same steps and enable it, and then try changing the story points of the Epics. Let us know if the rule succeeds in updating the Initiative.

[Nataliya Krymska]

Hello @Trudy Claspill 
Thank you very much for your advice - to check the "Edit" Issue step. 
It was typo there. That is the reason why rule was executed, but field was updated with "None" :)
Thank you again! 

Now I start to work on other use cases, for example, when Epic was created, broke down and later on assigned to the appropriate Theme and Initiative. 

I know I have to assign "Parent Link" change as a trigger to do the sum up.
Im going to start testing, hope I can post here questions if they appear. 

Thanks and happy Friday :) 


 

[Nataliya Krymska]

Hello @Trudy Claspill 
hope you're doing well :)

I have a question, hope you can help with.

I would like to run the "Sum Up" rule for Epics with the condition that the sum of story points in child items is greater than the story points number of the Epic.

As far I understand its impossible to do out of the box, is it true? Thanks

[Trudy Claspill]

You can add a condition to your rule to check if the sum of story points in the child issues is more than the value currently in the Epic, and only edit the Epic if this condition is met.

It seems that we have already solved your original questions/issues. If my guidance helped you with that please consider marking my Answer as Accepted.

[Nataliya Krymska]

@Trudy Claspill 
thank you very much for your advice. 
Advanced compare condition works great

[Trudy Claspill]

You're welcome.

Since your questions have been addressed please consider clicking on the Accept Answer button. That helps other community users find posts with validated solutions.