Because the Resolution field behaves in a very specific way which isn't obvious to new Administrators. They can put themselves in a bad state very easily (like by adding the Resolution field to the create screen) but getting out of it isn't as simple (this requires workflow changes and bulk operations).

With this kind of documentation customers can understand the impact of the use of this field and why JIRA behaves in this way.