#### Problems with this settings

* It adds a lot of complexity for development.
* It is unclear if there is anyone really using it.
* On our cloud offering, around 8% of subscribing accounts Begin of the insertionhaveEnd of the insertion Begin of the deletion use the status to setEnd of the deletion progress Begin of the insertionautomaticallyEnd of the insertion Begin of the deletion automatically, 89%End of the deletion set Begin of the insertionby status, 89% haveEnd of the insertion the progress Begin of the insertionset manually by field (which is the default),End of the insertion Begin of the deletion manually,End of the deletion 3% have disabled it. Begin of the insertion
* Out of the 89% people, we do not know how many people actually use the progress system at all. It could be only half of them, or only 10% of them.End of the insertion
* 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

<img class="op-uc-image op-uc-image_inline" style="width:427px;" src="/api/v3/attachments/88613/content">

**Migrations**

* Begin of the insertionWhen completion rate is set manually (from work package field)
* Nothing to do
* When completion rate is automatically set from status (from work package status)
* Work packages progress values need to be updated
* End of the insertion Case 1: Work is defined -&gt; The Remaining work is derived from % Complete Begin of the insertion
End of the insertion Begin of the deletion
End of the deletion * Case 2: Work is not defined -&gt; % Complete is deleted (since there is no value for Remaining Begin of the insertionwork)
End of the insertion Begin of the deletion work
End of the deletion * The aggregated values for the parents are re-calculated. Begin of the insertion
End of the insertion Begin of the deletion
End of the deletion * There is a journal in the work package explaining the change Begin of the insertion
End of the insertion Begin of the deletion
End of the deletion * We have tested the performance of migrations in large installations before the release and the deployments. Begin of the insertion
* Delete the setting

**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?
* 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.End of the insertion