Seems ops manager can not set Default Write Concerns to 1 when creating/modifying clusters

When I create a new cluster of mongodb 5.0, the “Default Read Concerns/Write Concerns” – “Default Write Concerns” – “w Option” must be filled with “majority” or a number, for example, 1

But the ops manager will set the option to {“w”:“1”, “wtimeout”:0}, not the expected {“w”:1, “wtimeout”:0}. Here the value of “w” is a string “1” which will be interpreted as a tag, not a numeric value 1

Seems to be an ops-manager bug. How to work around with it?