The test method history panel shows items which have same name but belongs to the different testsuite

[mkralik3]

Describe the bug
The history panel in the UI for a particular test shows also the results of all other tests from the same launch even though they are under different test classes. This happens only when I use jUnit5 client. When I upload junit xml manually via UI (as zip file with JUnit files), it works as expected (for a particular test method, it shows items in the history panel only which has the same testsuite name [see the image in the Expected behavior section]).

e.g.
I have 4 test classes (testsuite name)

DynamoDbSinkConnectorITCase
SftpSinkConnectorITCase
FtpsSourceConnectorITCase
FtpsSinkConnectorITCase

and all have the baseConnectorSmokeTest test method. (and also before/after methods)

When I upload test results via agent-java-junit5, and look at the latest test (FtpsSinkConnectorITCase > baseConnectorSmokeTest), I see (in the history panel) others baseConnectorSmokeTest items from that launch (and previous launches) which is incorrect because they belong under a different test suite name.

There should be only two items, one from launch #2 and one from launch #3.

Also, after that, if I click on one of those incorrect items (and it would be a failed test with a test log), it will show me a log that belongs under a different test suite because the path is not updated in the UI.: (selected test item and shows information is actually under SftpSinkConnectorITCase testsuite but the UI still shows FtpsSinkConnectorITCase)

Expected behavior
I should see there history across launches but only for baseConnectorSmokeTest which is under FtpsSinkConnectorITCase test suite. (not all with the same name with different parent item [testsuite])
When I upload the same test run manually ( via a UI as zip file with JUnit files), I see there history correctly (only one item from launch #1 and one from #4):

Dependency versions
agent-java-junit5:5.1.4
JUnit version: 5.8.2
RP version: API Service: 5.6.3; Authorization Service: 5.6.3; Service UI: 5.6.0;

(I don't know if the root cause of this issue is in UI or in the java / java-junit5 client so I have posted it here )

[tr1ble]

Hello, @mkralik3 , I hope you are doing well! As I've checked, current issue is not on UI side, so I think bug is on Java agent side (incorrect code ref generation, test case ids) or on Back end side during import. Can you check this out, @HardNorth please ?