ChatGPT DEVChatGPT DEV

PractiProject

Setup and Migration Page

Story Point Counted as completed

This setup item allows you to decide how and when issues are defined as completed. When an issue is completed, their story points are considered as value-earned. This means that for tracking accounting those issue will be considered as delivered. The accounting can be done in several ways - by the Jira issue Done status, through the issue being added with either a resolution or Done; or only to issues that were associated with a resolution (meaning that a resolution section has to be filled as part of issue resolution). Use the right setup that is appropriate your organization process.

To select the needed Story Point setup:

  • Click on the app admin menu option Setup and Migration

  • Find the section Story Point Configuration

  • Select your option

 

Planning and Tracking Effort Type

image-20240219-234512.png

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.

image-20240219-235045.png

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.