Script Runner aggregate function not working

swetha meti December 7, 2016

Whenever i fire the below query, i get the below error in JIRA.Could you pease assist. 

 

project = "XXX " AND type = Story AND Sprint in (2276, 2244, 2152, 2162, 2200, 2435, 2255, 2318, 2222, 2233) AND  issueFunction in aggregateExpression("Story Points" ,"QAStoryPoints.sum()

image2016-12-7 17:45:15.png

But when i give the below query, its working. Both Story Points and QA Story points are Field Custom Fields

image2016-12-7 17:45:47.png

 

5 answers

1 accepted

2 votes
Answer accepted
Jonny Carter
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.
December 7, 2016

I noticed that there's a colon in your field name. Perhaps that is the issue? ScriptRunner simply isn't finding your field because you're not asking for it by its name. 

0 votes
swetha meti December 7, 2016

Corrected the Field name by removing the colon and it works now.Thanks.

0 votes
swetha meti December 7, 2016

i did try putting a colon at the end of the field name, but its not helping.Below is the error.Should i edit the Field name and remove the colon for this issue to get resolved?

 

image2016-12-7 21:40:58.png

0 votes
swetha meti December 7, 2016

 Hi,

QA Story Points custom field is also a Number field.Attaching a screen shot.

 

image2016-12-7 20:18:41.png

 

image2016-12-7 20:20:18.png

0 votes
Jonny Carter
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.
December 7, 2016

They're both custom fields, but custom fields have types. What type of field is QA Story points?

If QA Story Points is a scripted field, then ScriptRunner will try to infer its type based on the searcher. JIRA Software's Story Points field is a Number field. What type is QASP?

Screen Shot 2016-12-07 at 2.35.16 PM.png

Suggest an answer

Log in or Sign up to answer