Content Organizer bug - PDF files does not get routed correctly if autodeclaration is on and library level default values are set

Question

It looks like whenever one specifies Column default values at a library level then the content organizer routing goes a bit awry SPECIFICALLY FOR NON OFFICE FILES [e.g. PDF] . Below are the observations and issues
1. Column level default value set on a record library with auto declaration of records turned on.  The content organizer routes the document to the library but also keeps a copy of the document in the drop off library. It does not remove it from the drop
off library. The instant we clear the default value settings at the library level of the target library the content organizer works as expected again. 
2. If default value settings are specified on a column in the target library then the PDF file gets routed to the document library but all the metadata is blanked out. The copy of the file that remains in the drop off library has all the correct metadata but
the target library has blanked out metadata. 
Are the 2 observations described above by design or are they bugs? If so is there any documentation that is available that proves this because this does not make logical sense and proving this to a client in the absence of any documentation is a challenge.
The problem goes away if we shift the default value to the site columns directly at the site collection level. It's just the library level defaults that the pdf files do not seem to agree with

Answer 1

Hi Lisa,
Thanks for responding. This can be replicated in any environment but is only replicable for a specific combination of content organizer settings . The combination of settings I am referring to can be seen in the screenshot below. If you turn off redirect
users to the drop off library for direct uploads to libraries and if you turn on sharepoint versioning then you should be able to replicate the issue. Also we are using managed metadata site columns. I simplified this use case to a custom content content type
with just 2 custom managed metadata columns and can still replicate the issue in several environments. Also note the issue does not occur if the default values are set at the site or site collection level. It only occurs if you set the column value default
at a library level.  I was able to replicate this on a completely vanilla Enterprise records site collection freshly created just to test this.  Also note that the issue is not that the file does not reach the destination library. The issue is the
document does not get removed from the drop off library after it is transfered to the destination library which technically should have gotten removed.