Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Rules Fields does not contain "Story point estimate"


I'm trying to create a rule in the automation app but for some reason the field name for the "Story point estimate" does not exist.

I've also tried using all the other "Story Points" field names but they don't invoke the rule.

Please Help.

In the Rule editor:

Screen Shot 2020-05-22 at 16.15.41.png

This is the field i'm using in the board:

Screen Shot 2020-05-22 at 16.15.22.png

1 answer

1 accepted

0 votes
Answer accepted

Hello @ehud

Thank you for reaching out.

Per your description, I understand you are trying to configure an automation rule (Under project settings > Automation), however, the triggers, actions, and conditions do not display the "Story point estimate" field. Is that correct?

Please, allow me to provide you some concepts about the behavior you are facing so we can confirm we are on the same page here:

I'm afraid the Jira Automation does not work properly for Next-gen projects and do not recognize the Story point estimate field, as explained in the bug reported below:

Two 'Story point estimate' fields in Jira cloud - one is called 'Story Points' the other is 'Story point estimates' 

We are currently working to fix the bug above, so please keep an eye open on that to receive any updates about its fix implementation. As a possible workaround, you can migrate your issues to a Classic project and use the field Story points to estimate it, which displays properly in Automation rules.

Additionally to the information above, I would like to make sure you know that the Story Point Estimate field was created to estimate issues only in Next-gen projects. This field will not work to estimate issues in Classic projects, where you should use the Story Points field, as explained in the top answer of the thread below:

Story point and story point estimate (duplicate?) fields 

Let us know if you have any questions.


Thanks for that detailed explanation :)

I finally managed to "hack it" by using JQL with the field key for that comparison.

But it would be better when you fix the issue of course.





Like # people like this

Hello @ehud 

I'm glad to know you were able to work around your issue. Thank you for providing this information!

Have a nice day.

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

1,452 views 11 22
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you