Symbology - changing the Value should NOT update the Label

[StephenLead]

In Graduated Color or Graduated Symbol symbology, ArcMap allows you to set the Label to read whatever you want, rather than exactly what is shown in the Values column.

 
The problem is that the slightest change to ANY value in the Range column completely obliterates all of the other labels, potentially wasting a huge amount of time.

Eg, if I change the first Range value to be 250001 this is the result:


The logic should be that the Label is set to the Range when the Classification is first set (including on layer creation) but thereafter, any changes to the Label field are made by the user only, not automatically.

[RTPL_AU]

@EdiePunt Do you want to make a note or should I spend the time to lodge a new idea to make this a global setting?
I don't see a scenario where I would want Pro to change the legend unless I explicitly tell it to. Having to go in to change this every single time for every layer seems so inefficient?

[SimonSchütte_ct]

@RTPL_AU  I fully agree, keeping customisation unless you reset them should be a global default setting. 
Similar idea: Keep Settings when changing Symbology for a Layer - Esri Community

[SimonSchütte_ct]

"Is it possible for Esri to add the version to the 'Implemented' tag? 
For all intents & purposes Ideas are not implemented if it is not a version paying customers can actually access. " @RTPL_AU good point! -> Add Version labels to ideas - Esri Community

[EdiePunt]

@RTPL_AU and @SimonSchütte_ct Thank you for your continued feedback. Ideally, a workflow would establish symbol classes first, then adjust labels when classes have been established. For cases where the data is often updated, we provide this new option that you can set for those layers to ensure that the symbol class labels are not overwritten when the class values change.

[RTPL_AU]

@EdiePunt Ideally, in the real world, clients would not give any feedback after something was created but, alas, that is not the case.
I (will) appreciate the new option - once we can use it reliably in a product we can access. 

It would be of more value if it can be set globally as we work in the real world where people change their minds or we re-use symbology from previous jobs that just need a few tweaks.  Having to go in and change this for every single layer, in case we may have to change the class values for that layer,  is just not efficient.  

From a UX perspective I cannot work out how the default behaviour is the one that WILL cause users pain? If you(Esri) is honest, every user HAS to set the option to not overwrite, every time, just in case they want to tweak anything.  
It's like putting your seatbelt on - most of the time you wont need it in hindsight, but you ALWAYS need it before you head off somewhere.


On the flip side - seeing the dodgy work that circulates out there, there are many people using Pro that don't give a hoot what their work looks like & are happy with 6 decimal place legends, as long as they beat the deadline they were given.