Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Roll up other fields than Sprints, Releases and Estimates in the fields section.

jeroen_wilmes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 28, 2023

I'm using Plans (advanced roadmaps) in Jira for project management. for some issues, on different levels (Epic, story or subtask) we have costs (both budgets and actuals) I created 2 different custom fields. In one the budgets are logged and in the other one the actuals. 

I have made some progress and have an automation rule that works almost.

The automation works. It selects the issues I like to roll-up, it does the math correct, but it seems that there is something wrong with the configuration of the field, although it is a number and all fields get a default value of 0; I get the following message:

"Edit issue

Could not convert the field value to a number. Please ensure the value is a number, math expression or smart-value that can be converted into a number.
Budget: 7.0.
No fields or field values to edit for issues (could be due to some field values not existing in a given project):
FOR-14"
The calculated value of 7 is the correct value, which is the sum of the values for this field of the to be selected issues.
Could it be caused by the "." in 7.0.?  
Can someone help me with this?

1 answer

1 accepted

0 votes
Answer accepted
Bryce Lord
Community Champion
June 29, 2023

Hi @jeroen_wilmes ,

Number field values can only contain a single decimal point, so the second decimal in "7.0." is more than likely causing an issue.

Let us know if that clears things up!

jeroen_wilmes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 29, 2023

Hi Bryce,

 

That is what I think as well, that causes the problem. However in the field in fill in "7" the smartvalue math makes 7.0.  

I use:

{{lookupIssues.customfield_15210.sum}}.

Bryce Lord
Community Champion
June 29, 2023

Hmm can you try removing the decimal at the end of your smart value expression?

jeroen_wilmes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 29, 2023

I changed to:
{{lookupIssues.customfield_15210.sum.round}}.

was a wild guess to just add it after the sum, but it seems to work.

thanks a lot.

Like Bryce Lord likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events