Cannot Set Story points for Epic via Automation

mo June 3, 2023

I've used the popular Video tutorial on how to setup Summed up Story points for epics, but I'm getting this strange error which suggests that the Story points field in epics is a custom value? Even though it's showing up in the Available fields list?

The Lookup Table JQL, etc, is all working as expected. If I set the value for another field, it seems to work ok.

UNKNOWN FIELDS SET DURING EDIT, THEY MAY BE UNAVAILABLE FOR THE PROJECT/TYPE. CHECK YOUR CUSTOM FIELD CONFIGURATION. FIELDS IGNORED -
Story Points (customfield_10014)

Screenshot 2023-06-04 at 2.40.38 pm.jpg

Screenshot 2023-06-04 at 2.40.02 pm.jpg

2 answers

2 accepted

1 vote
Answer accepted
mo June 4, 2023

Thanks @Bill Sheboy 

I ended up using the Additional fields section with the following and it worked!

{
"fields": {
"Story point estimate": {{lookupIssues.Story point Estimate.sum}}
}
}
0 votes
Answer accepted
Bill Sheboy
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 4, 2023

Hi @mo -- Welcome to the Atlassian Community!

Are you using a Company-managed project (CMP) or a Team-managed project (TMP)?

CMP use the "Story points" field (and smart value) and TMP use the "Story point estimate"...even though they have the same name in the UI.

Your rule appears to be referencing both, although only one should be relevant.

Kind regards,
Bill

mo June 4, 2023

Thanks for the response.. I'm using a TMP, the issue is there is no option to selection "Story Point Estimate" from the UI, only "Story points".

Suggest an answer

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

Atlassian Community Events