Declaring a transition of \'Open/Closed\' from \'Any\' to \'Open\' to automatically set \'Privacy\' to \'Private\' is accepted but has NO effect.
On the contrary declaring a transition of \'Status\' from \'Any\' to \'Fixed\' to automatically set \'Open/Closed\' to \'Closed\' does work NICELY.
1] What is the difference ? ... in the first case, the field for which the transition is declared has a \'System\' scope whereas in the second case it has a \'Project\' scope ... would that explain it?
2] Anyway, how is it possible to set/change the default value of a field?
3] In the end it turned out that the only way to force \'Privacy\' to \'Private\' was:
- declare \'Privacy\' as mandatory
- declare its transitions to be \'Forbidden\' by default
- declare the transition \'Any\' --> \'Private\' allowed

It works but in my opinion it\'s far from being intuitive.
... and in addition if we don\'t declare \'Privacy\' as mandatory
and submit a bug without setting this field, the bug is created with \'Privacy\' set to \'Public\' which is contrary to the defined
transitions.
All these points should be clarified and fixed/explained.
Yves