Hi,
I've recently tried to set up a rule that sums all story points to the epics on a specific project (see screenshot for more details):
(*) Note: on the Edit Issue Fields action (last step), "AVR - Epic SP (Sum)" is the name of the custom field I've created to store the sum of story points. The smart value I'm using for this one is:
After testing and checking the audit log, looks like everything is working fine but the calculated custom field is not getting any update.
Any clue?
Thanks a lot in advance.
Can you give the details of your edit action in the branch?
I suspect it is something like: {{lookupIssues."AVR - Epic SP (sum)".sum}}, replace this with customfield_xxxxxx
Thanks for replying! Here are the details:
Already tested and still no change on the custom field:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are there issues related to the Epic that have not been estimated?
If so can you try the clause: {{lookupIssues.customfield_21401.sum|0}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes,
Both US are linked to the epic:
After using the clause, nothing changed. Still value 0 for the custom field - the audit log keeps registering a success somehow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I do sense the issue then lies in the fact that the Epic contains issues from another project, linked to the Epic.
What if you change the automation rules to run on both projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In this case, both Epic and Stories belong to the same project.
Regarding the automation, it's only applying to this test project specifically.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I see the issue now, your lookup should be in the branch not before.
I tested this, see my example.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That was my initial setup of the rule, but changed it after checking another thread where I saw this alternative. But none of these worked for me.
My sensation is that the smart value on the edit issue could be the key to solve this, as the audit log is showing that the rest of the rule is properly designed (issues passing and actions performed)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you using the correct Story Point field, do you have multiple?
This rules works on my side.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As a reminder, custom fields are not yet supported for lookup issues with Data Center: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 Although they should not be needed for the scope of this question.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To isolate the problem, I recommend writing this to the audit log after the Lookup Issues action, then re-test your rule:
Story point values: {{#lookupIssues}}{{key}}:{{Story Points}}; {{/}}
Story points sum: {{lookupIssues.Story Points.sum}}
That will confirm the values are set for the issues in the lookup result.
And what is the type of the custom field where you are trying to store the result?
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you give a try with the below approach and see if this helps ?
"Epic Link" = {{triggerIssue.epic link}}
This gathers child issues for the epic, enabling story point summation.
{{lookupIssues.Story Points.sum}}
Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for replying - I already tested that solution, as I found somewhere this: Automation For Jira - How to create a rule that sums up the story points from stories to a linked epic | Automation | Atlassian Support, which is pretty similar to what you've shared.
Still not worked for me - note that I'd like to store that sum on a custom field, as my intention is hiding it after and just act as data storage for some reports.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.