There are two (2x) options for how to configured the Story Points field in a Jira Project/Space that is used by a Team. These two options are: Auto-detect and Manual. The details are:

To manually override any auto-detected Story Point field mapping, you need to make the configuration change on the Team Mapping, under the RTE Cockpit > ALM Connection > Team Mapping > Advanced Mapping section.

By default piplanning.io will look for a field named Story Points on the Jira Create Issue Screen of any Work Item (Issue Type/s) that are synchronized (on the #3 Team Board).

If that Custom Field with the label Story Points in a Jira Project/Space is found [again, on the Create Issue Screen], it will use that field to sync the Story Points entered on the Sticky Note to the Work Item in Jira, and vice versa.

If a Team estimates their work using a different field and method (other than Story Points), such as using estimates in Hours as a unit of Time, then you can manually configure our Sticky Note Story Points field to sync with that specific field in Jira.

To manually set the Story Point field on a Team is simple. You will be provided the list of fields that are supported on the mapped Jira Project/Space in the RTE Cockpit > ALM Connection > Team Mapping > Advanced Mapping section.

With the ability to manually configure what field in Jira is used to synchronize the Story Points field, we support the use of the Jira Original Estimate via the Jira Time Tracking field.

Jira's Original Estimate and Time Tracking fields let teams plan, log, and monitor actual labor hours spent on User Stories or team-level Work Items.

Definition: The initial prediction of how much total time a task will take to complete (entered in minutes, hours, days, or weeks—such as 4h ).

Difference from Story Points: Story points measure relative complexity and effort, whereas the Original Estimate measures absolute clock time (hours or days).

That's it. The Team now can enter a numeric estimate on the Sticky Notes in piplanning.io and a single unit in the Sticky Notes Story Point field, equals that unit in hours in Jira on the Original Estimate and Time Tracking field.

Note: We display the Time Tracking field to be selected instead of the Jira Original Estimate due to the data type/data schmea on the Jira side). The Time Tracking field does hold the Original Estimate value.

We support two different field types in Jira:

This field must have numbers as options (0, 0.5, 1, 2, 3, 5...)

If you use a custom field type or other field type for Story Points which is not named Story Points, you can define that custom field type per Jira Project mapping in the ALM Connection | Team Mapping page.
​

You need to specify your field in the following syntax:

Make sure that you have the field named Story Points on the default (or Create) Issue Screen in the Jira Project you are using. Make also sure that the Custom Field named Story Points is available on the Issue Type you want to sync (check Custom Field Settings in Jira for that).