How piplanning.io Synchronizes Story Point [Estimates]
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:
Auto-detect will use the Jira Field Name Story Points if it is found in a Jira Project > Create Issue Screen.
Manual to configure a Custom Field on the Jira Projects > Create Issue Screen that holds a numeric value or the Time Tracking field which will sync with the Jira Original Estimate field in the Jira GUI.
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.
Auto-detecting the Story Points field
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.
Manually configure the Story Points field used on Jira Work Items
If a Team estimates their work using a different method, such as estimates in Hours or a unit of Time, then you can manually configure the Story Points field in piplanning.io.
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.
Supported Jira Original Estimate Field for Story Points
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 or Jira Time Tracking fields.
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 or 2d).
Difference from Story Points: Story points measure relative complexity and effort, whereas the Original Estimate measures absolute clock time (hours or days).
Note: 1 point in the Story Point field is stored as 1 hour in the Time Tracking > Original Estimate field. So, 1.5 Story Points on the sticky note in piplanning.io will sync as 1.5 Hrs or 90 m in Jira and vice versa.
Supported Custom Field Data Types for Story Points
We support two different field types in Jira:
Numeric field
Options (Single Select) field
This field must have numbers as options (0, 0.5, 1, 2, 3, 5...)
Previous: Custom Field Story Point Setting
(This method is being phased out)
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:
|
Troubleshooting: Story Points are not synced to stickies on the Team Board?
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).
Keep in mind that we cache the available fields in Jira for up to 45 seconds.
Make sure that you wait at least 45 seconds after you have changed something in Jira. If you are working with an existing PI Session already setup with Jira, restart the sync to clear additional caches.