Automation to update field based on Delivered Story points

[Tere Pile]

I have it set on schedule, weekly if status is 'pending sign off' and if Custom Field is empty

I want the total storypoints 'delivered' / 30 set to FieldX as a whole number. 

Rovo indicated: {{issue.<delivery_sum_field_smart_value>.divide(30).round}}

I tried replacing words w/custom field {{issue.customfield_13938.asNumber().divide(30).round}} 

Both runs show 'sucessful' but field is not updating. Assistance please 

[Tanguy Crusson]

Hi @Tere Pile , one thing I can think of it: what issue are you running this rule on? It would have to be on the linked delivery epic, not the idea itself.

[Bill Sheboy]

Hi @Tere Pile 

For a question like this, context is important for the community to help.  Please post the following:

• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution

Until we see those...

Do you already have a custom field in your JPD space / project with that "total story points delivered", or do you want to gather the Story Point values from the linked, Delivery Tickets for the JPD Idea?

If you have a custom field in the JPD space / project, what is its type: number, text, etc.?  The type will determine how to perform the math operations needed.

Kind regards,
Bill

[Tere Pile]

Rule is pretty basic - scheduled & Edit items (no branching) - 2 steps

Rule is in Discovery 'idea' @Tanguy Crusson,  this is likely the issue, but until Atlassian frees up more automation for the poor people in software, not an option to move this to that side of the fence.  

@Bill Sheboy no custom field for total story points (because i can see that in delivery field).  It is a Custom Field in Discovery for the result value (number)

If the issue truly is this has to be run on software, we'll live w/manual process for now.  I will say however, the automation if I left it on does show 'Successful' - which technically is incorrect as nothing was updated. 

Audit log info: 01/06/2026, 14:45:56
6894592692
Edits post closure SUCCESS 7.19s  
Scheduled01/06/2026, 14:45:56
Edit work item01/06/2026, 14:45:57
Issues edited successfully
PPDE-2413, PPDE-2419, PPDE-2414, PPDE-2454, PPDE-261, PPDE-2417, PPDE-305

[Bill Sheboy]

Hi @Tere Pile 

Without seeing your specific rule's details, and assuming your JPD project is PPDE, this may be a project scoping problem...and the suggestion from Rovo is likely wrong.

Let's assume you want this:

GIVEN one or more Ideas
AND each Idea has zero or more linked Delivery Tickets in software projects
AND Ideas have a custom field named "Total Story Points Delivered" to sum the linked Delivery Tickets' Story Points
WHEN time passes on a schedule (e.g., daily)
THEN the Story Points in the Delivery Tickets are summed for an Idea to set the custom field

Thus, the rule could look like this:

• rule scope is multiple projects, including the JPD and software projects 
• trigger: scheduled, with JQL to gather the Ideas to update
• action: lookup work items, with JQL to find the linked work items in the software project
• smart values condition: check if any work items were found
  • first value: {{lookupIssues.size|0}}
  • condition: greater than
  • second value: 0
• action: edit work item, setting the custom field to your value with a math expression using the ROUND function:

{{#=}}ROUND( {{lookupIssues.Story points.sum|0}} / 30, 0){{/}}

[Tere Pile]

Thanks will try that, didn't want a new field but if necessary and saves me time :) I'll try it, thanks will advise! 

[Bill Sheboy]

@Tere Pile -- I thought you already had a custom field for the sum.  Where did you want to store the value?

[Tere Pile]

Clarification: I have a custom field for the new calculated sum (i.e. the sum of story points/30 = X) , but not for the sum of story points

[Bill Sheboy]

Do you need both values or only the sum / 30?  If you only need the divided amount, the sum function in the math expression will handle the rest.

[Tere Pile]

I just need the sum/30 value - is what rule has right now 
Scheduled Query pulls Ideas applicable ideas
Then Edit field 'set' is: {{issue.customfield_13938.asNumber().divide(30).round}}

[Bill Sheboy]

Hi @Tere Pile 

If customfield_13938 is already a number type, it does not need the asNumber conversion.

And, how are you setting the value of customfield_13938?  If that is one of the JPD calculated / formula fields, this approach will not work.  Those formula fields in JPD are for display-only in the UX, and the value is not stored in the Idea.  A common workaround is to use an automation rule to perform the sum (and any subsequent math operations) rather than using the JPD formulas.

[Tere Pile]

ok that triggered the missing piece (I think) sorry working this between presentations on process updates ;) so checking rule again - I was missing the points value part, I only had update custom field - so rechecking // closer maybe but 
Schedule is good - that seems to work: 
Then: Edit work item field
Field: zFinal  (which is the custom number field to update) 
More Options - added: 
{{#=}}
{{#if(issue.deliveryProgress.pointsDone)}}{{issue.deliveryProgress.pointsDone}}{{else}}0{{/}} / 30
{{/}}
This produces a warning that says rule has to run to validate, manually ran rule (made sure since last was unchecked) fails: "Unknown unary operator / at character position 1"

Since the query is finding 5 'ideas' to update
Gut says I need to re-fetch because there are 2 items to update, except I have the 'check' in schedule so it should run for each. 

Just not sure how do that part

@Bill Sheboy 

[Bill Sheboy]

Answering those questions in reverse order...

When using the Scheduled trigger with JQL to loop over the work items, a re-fetch action is not needed for what you show.  If your rule steps later wanted to use the updated value for something else, adding a re-fetch would help.

Next, assuming your smart value is correct for the field, you have the incorrect syntax for the conditional expression to use an else.  That one does not use the pound # symbol.  Please try this one:

{{#=}}{{if(issue.deliveryProgress.pointsDone, issue.deliveryProgress.pointsDone, 0)}} / 30{{/}}

Or, try using the default value with the pipe | character:

{{#=}}{{issue.deliveryProgress.pointsDone|0}} / 30{{/}}

To confirm the smart value for your field, you may use the { } lookup at the right-side of the edit field or use this how-to article:

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

[Tere Pile]

@Bill Sheboy thanks for the information - best i can tell smart doesn't exist. it's giving me a json error now, I need to play w/the debug - later, back to some reporting due! 

[Bill Sheboy]

Perhaps also try the custom field ID instead of the smart value in the expression / JSON.