Team Managed Projects: Trying to set story point estimate in next-gen project via automation is choosing the wrong field

Issue Summary

When using a next-gen project in Jira Cloud, and attempting to setup an automation rule in order to create a new issue based on any trigger, if you attempt to set the Story Point Estimate field on that new issue, it will fail.  The issue is still created, but that value cannot be set by the expected means.

Steps to Reproduce

1. In a next-gen project, Create an automation rule with any trigger (manual for example)
2. For the action, select 'create new issue' and choose inside same project (by project key)
3. For this example, I selected to create a new Task type issue
4. Attempt to use the drop down box to select which fields to set, and choose "Story Points"
5. Choose a numeric value for that field to set (example 57)
6. Publish/save run
7. Trigger the automation to run

Expected Results

We expect that a new issue is created and the story point value is 57

Actual Results

Issue is created, but story point estimate value is not set. Automation audit log shows an error like so:

Unknown fields set during create, 
they may be unavailable for the project/type. 
Check your custom field configuration. 
Fields ignored -Story Points (customfield_10044)
Issues created successfully

However customfield_10044 is not the Story Point Estimate custom context field in this Next-gen project, but rather the global custom field used for classic projects.  Instead in this case, I found that in my instance the custom field is actually customfield_10088 in this project

Workaround

1. First in the Choose fields to set, uncheck Story points (this is technically the wrong field)
2. Then at the bottom of the page, scroll down to More options,
3. In more options, manually set the field using json like so:

   {
       "fields": {
           "Story Point Estimate": 57
           }
   } 

4. Save/publish run