#### Begin of the insertion<img class="op-uc-image op-uc-image_inline" style="width:427px;" src="/api/v3/attachments/88613/content">End of the insertion Begin of the deletion Problems with this settingsEnd of the deletion

Begin of the insertion#### Reasons for the change

End of the insertion * Begin of the insertionWork flows for status transitions are different from permissions to change % Complete
* End of the insertion It adds a lot of complexity for development. Begin of the deletion
* It is unclear if there is anyone really using it.End of the deletion
* Begin of the deletion On our cloud offering
* 88% use field (progress set manually)
* regarding progress %
* 15% have no work packages with progress set
* 20% have between 1 and 9 work packages with progress set
* 65% have at least 10 work packages with progress set
* regarding work
* 22% have no work packages with work set
* 33% have between 1 and 9 work packages with work set
* 45% have at least 10 work packages with work set
* 9% use status (progress set automatically via status)
* regarding work
* 28% have no work packages with work set
* 27% have between 1 and 9 work packages with work set
* 45% have at least 10 work packages with work set
* 3% disabled
* End of the deletion It&#39;s hard to draw conclusions about how many people are actively using the progress system: they may have tried it in the past and then stopped using it.
* The feature simply does not work.
* There is no differentiation between project, work package, types and status.
* It is not possible to set the field remaining work

Begin of the insertion#### Acceptance criteriaEnd of the insertion Begin of the deletion <img class="op-uc-image op-uc-image_inline" style="width:427px;" src="/api/v3/attachments/88613/content">End of the deletion

Begin of the deletion **Migrations**

End of the deletion * Begin of the insertionRemove the settingEnd of the insertion Begin of the deletion When completion rate is set manually (from work package field)
* Nothing to do
* When completion rate is automatically setEnd of the deletion from Begin of the insertiontheEnd of the insertion status Begin of the insertiondefinition.
End of the insertion Begin of the deletion (from work package status)
End of the deletion * Begin of the insertionThereEnd of the insertion Begin of the deletion Work packages progress values need to be updated
* Case 1: WorkEnd of the deletion is Begin of the insertionno connection between status changes andEnd of the insertion Begin of the deletion defined -&gt; The Remaining work is derived fromEnd of the deletion % Begin of the insertionComplete.
End of the insertion Begin of the deletion Complete
End of the deletion * Begin of the insertionThereEnd of the insertion Begin of the deletion Case 2: WorkEnd of the deletion is Begin of the insertionno connection betweenEnd of the insertion Begin of the deletion not defined -&gt;End of the deletion % Complete Begin of the insertionand status changes.

#### **Migrations**

The goal of the migrationsEnd of the insertion is Begin of the insertionto achieve a consistent status and correct calculations.

End of the insertion Begin of the deletion deleted (since there is no value for Remaining work)
End of the deletion * Begin of the insertionExistingEnd of the insertion Begin of the deletion The aggregatedEnd of the deletion values for Begin of the insertion% CompleteEnd of the insertion Begin of the deletion the parentsEnd of the deletion are Begin of the insertionnot deleted.
End of the insertion Begin of the deletion re-calculated.
End of the deletion * Begin of the insertionIn caseEnd of the insertion Begin of the deletion There is a journal inEnd of the deletion the Begin of the insertion% Complete is not consistent with Work and RemainingEnd of the insertion work Begin of the insertionwe show a warning messageEnd of the insertion Begin of the deletion packageEnd of the deletion explaining the Begin of the insertionproblem and giving information about resolving it.
End of the insertion Begin of the deletion change
End of the deletion * Begin of the insertionInconsistent values are excluded from calculations.
* When clicking on anyEnd of the insertion Begin of the deletion We have tested the performanceEnd of the deletion of Begin of the deletion migrations in large installations beforeEnd of the deletion the Begin of the insertionvalues (Work, Remaining workEnd of the insertion Begin of the deletion releaseEnd of the deletion and Begin of the insertion% Complete)End of the insertion the Begin of the insertionmodal opens.End of the insertion Begin of the deletion deployments.End of the deletion
* Begin of the insertionInEnd of the insertion Begin of the deletion DeleteEnd of the deletion the Begin of the insertionmodal the user can achieve a consistent state. Inconsistent states can not be saved, e.g missing Work and Remaining work. The modal can be cancelled.End of the insertion Begin of the deletion settingEnd of the deletion

**Open questions**

* CB: &quot;% Complete is deleted&quot; -&gt; I understand that it&#39;s now possible for % Complete to be unset. Before that, % Complete was automatically set to 0% and could never be unset. Did I understand correctly? Begin of the insertion
* NL: % Complete is always calculated from Work and Remaining work. It is not possible to unset it.End of the insertion
* CB: I feel like the migration to update the calculations belong to ##40749:
* migration for this work package should only update the % Complete field according to the status and delete the setting. This is necessary because actually the setting does not change the % Complete value, but only the way it is displayed: it displays the value from the status instead of displaying the value from the % Complete field. When switching the setting back and forth, we can see that no data is lost.
* then during the development of #40749 the migration should be done as you describe above, making sure that work, remaining work and % complete are consistent with each other and according to the new defined business rules. Begin of the insertion
* NL: I updated #40479 accordinglyEnd of the insertion