In our project somebody translated Story-Points into German and renamed the "Story-Points" custom field accordingly. This causes this plugin to not write the final estimate into our story-points field.
Additionally Atlassian itself introduced a new story-points field with their next-gen projects (see https://jira.atlassian.com/browse/JSWCLOUD-17173 ) named "story point estimate".
Currently the STORY_POINTS_FIELD_NAME is hard-coded in IssueServiceFacade.java#L43.
In our project somebody translated Story-Points into German and renamed the "Story-Points" custom field accordingly. This causes this plugin to not write the final estimate into our story-points field. Additionally Atlassian itself introduced a new story-points field with their next-gen projects (see https://jira.atlassian.com/browse/JSWCLOUD-17173 ) named "story point estimate".
Maybe the field for the final estimate should be configurable similar to the board configuration which field to show as estimate (see https://confluence.atlassian.com/jirasoftwareserver0820/configuring-estimation-and-tracking-1095248570.html )