Issue Summary

If the Default story point field configured for the instance is not actually named Story points, it's still shown as story points in the AR plans. And this will lead to confusion

Steps to Reproduce

1. Rename the story point field
2. Configure a plan to use Story points as estimation

Expected Results

The plan will show the correct name of the field

Actual Results

It shows Story points regardless of the new name

Workaround

Rename the field back to story points, you might need to contact cloud support to correctly identify the field ID