nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Codebeamer mappedSelector issue

medini_1073100661

Hello Scripting Forum,

I am facing an issue with mappedSelector during importing objects from Codebeamer.

Based on an attribute I filter the objects which need to be pulled. When there is an object which does not meet the criteria, the filtering function returns false meaning there is no applicable typeMapping in the mapping file remaining in this particular example I attached. In that case I get an import error.

It works in the other way around when it comes mappedSelectors during pushing requirements.

My theory is that somehow it is not handled when there is no matcing typeMapping when objects being pulled. Do you have an idea what is causing that?

I attached the mapping file and script.

Thank you for the support!

Best regards,

Krisztian

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1040289819

Hi, the issue has been fixed in the recently released version 2025 R2.02 of medini analyze.

Regards

Olaf.

All comments

medini_1024169437

Krisztian, I am not sure, I need to reproduce this. Could you show the error that is reported?

Which version of medini are you using? Your scenario somehow rings a bell.

Jan

medini_1024169437

Krisztian, I could reproduce I think. You actually hit a limitation / aka defect which is in the connector since the first implementation that we did together with Intland back in 2020 :-(

I am sorry to say but I dont see a way to workaround this, you must match a type, the connector does not accept that no type matches (as the other connectors).

I will file a defect and we may fix this in next service pack.

Regards

Jan

medini_1024169437

One additional remark: the mappng file refers to test_cb.js but the file is named .testcb.js

Jan

medini_1073100661

Thank you!

medini_1040289819

Hi, the issue has been fixed in the recently released version 2025 R2.02 of medini analyze.

Regards

Olaf.