• When creating a Pipeline Library in a folder, I receive no warning when the "default version" field is left blank"

• If the "default version" is left blank, Pipeline scripts cannot properly load the library, and users see an error in the build job console like this: ERROR: No version specified for library mylibraryname

• Adding a "default version" that matches the git branch like "master" works properly here

• Also, after adding "master" a confusing warning message also appears:
  When using Legacy SCM, you will need to include ${library.zotty.version} in the SCM configuration somewhere.

Expected Outcome:

• The warning text should appear when the default version field is left blank. Once the default version field is populated with a value, there should be no warning.
• The warning text should be made clearer that this is only a warning because no default library version can be determined, either specify a version in the field – or include the ${...} tag in the script.