I believe it used to be 1. I prefer 0. We actually DO use 0* but that's not why. The reason is that we almost never use 1. It's almost always a very specific amount like .2843 or 1.0649.
 
*we enter Labor as a BOM item but use Routings to calculate Standard Labor Costs. We put Labor on the BOM so that when we add labor we don't get the warning/question "The item is not on the BOM, are you sure you want to add it?". But we don't want any actual labor on the BOM because then it will artificially inflate the Total Standard Cost. For some reason, the Import BOMs utility will not allow a 0, so our imported BOMs have a Labor Qty of .00000001.

I guess it depends how it was set up.
 
If the "1" was selected (highlighted) when you reached the field it wouldn't matter, as you could just type whatever you want, or if you wanted 1 then you could enter past or just save.
 
However, if it's NOT highlighted then you have to delete it, which is an extra step. And I would be pretty sure something OTHER than 1 is used more often than 1 by the masses.

Quote from dkinser on 03/29/13 at 06:03:30:

 
Exactly. But not always "1". By leaving it blank the user can put in anything they want.
 
Personally, I can think of a host of things that need to be FIXed before niggling enhancements such as this are offered...

www.istechsupport.com/bugtrack/

the qty thing is killing me
 
we use 1 90 % of the time my fingers are not adjusting to zero well