Due to Jenkins limitations, we are supporting result files only using the encoding UTF-8

Due to Jenkins limitations, we are only supporting reports using the encoding UTF-8 when importing Execution Results
If using the encoding UTF-8-BOM, it returns an error as described in the following example.

Steps to reproduce

Step	Result
Using a JUnit XML report encoded as UTF-8-BOM
Importing the JUnit report (UTF-8-BOM)