...
...
Story Points
This setup allows you to decide how issues are defined as completed. When an issue is completed, their story points are considered as value earned. When tracking they will be counted as delivered. The accounting can be done through Jira issue Done status, through issues added with a resolution or done; or only to issues that were associated with a resolution.
...
Click on the app admin menu option Setup and Migration
Find the section Story Point Configuration
Select your option
...
Planning and Tracking Effort Type
...
The planning and Tracking Effort Type controls the way the effort units (time or story points) are used in your planning.
When on Project board (the default setting). The units used are those that are set in the board you are using.
When select manually is used, a toggle is displayed in the Planning % Tracking tab. Allowing the user to select time or story points irrespective of the board setup.
...
Issue Changes during active sprint
This setup allows you to control how strict you are in sprint planning. You may want to prevent your planner from changing sprint commitments AFTER the sprint was launched. With this state, changes that are done in effort during the sprint will not be accounted for in tracking metrics. Alternatively, you may allow in-sprint effort updates, as the team learns about them.
Note: In the default setting Freeze estimation at sprint launch of the app, issue estimations are frozen at the moment a sprint becomes active. If estimations are changed during the sprint, that change is not taken into account (as this is post “planning”). This will be perceived as a difference between the changed, new, effort of issues, and the values in the tracking panel - which can be confusing.
...
Note: When an issue is (removed and added) to an active sprint, the modified issue is taken in account with its lates effort value. This will resync the tracking calculation.
Virtual Expert
This option allows you to enable (default) or disable the Virtual Expert feature.
...