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; } } }

Import of Associations from CodeBeamer

medini_1005899080

Hi, is there a possibility to import associations from codeBeamer? (e.g. as trace or contribution) Thanks, Sven

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

Sven, we can import "Reference" attributes but not Relationships at the moment. Jan

medini_1005899080

Hi Jan, is this also possible within CodeBeamer?: and: what is the mappedRelation in codebeamer? Thanks, Sven

medini_1024169437

Hi Sven, I copy paste here a recipe to create a "Reference" attribute which could be used as "mappedRelation": How to create a Reference attribute? (in 8 steps) Go to the "Trackers" page Select any tracker in the tree and use "Configure" Select the "Fields" tab Got to the bottom and use "More Fields..." drop down, go for "New choice field" Configure the "Datasource" to "Work/Config Items", check "multiple" if you like Select one or more projects and target trackers Note: if you select only ONE tracker, you won't be able to create cross-module (cross-tracker) links! Note: if you dont select any tracker it wont work! Press OK to create and return to the "Fields" page, you MUST save to get changes applied Use the "Label" in the mapping later

medini_1005899080

Thanks Jan. Is there a possibility to distinguish beween different types of "traces"? e.g.: FTTI Trace shall be mapped to FTTI Attribute in codebeamer, SafeState Trace shall be mapped to SaSt Attribute in codeBeamer? otherwise all traces are mapped to FTTI, right?

medini_1024169437

That should be possible Sven, you can map multiple remote relations/references to Trace. Assume you map CB reference A to Trace and B to Trace, as a result, all A references will create Traces with kind "A" and all B references will create Traces with kind B. If you create Traces in medini and export, them to CB, only those with kind A and B will be considered and mapped/exported. Jan

medini_1005899080

Hi Jan, of course this is not working: Shall I use instead of "trace" the "kind" of the trace? Sven

medini_1024169437

Well, Sven, that exactly *should* work IMHO. What kind of problem do you face? Jan

medini_1005899080

medini_1024169437

Ah, I see. Hm, could you please try one thing: enable only *one* Trace mapping on first import. Once imported, enable the other (or more) Trace mappings and see how Push/Pull works. Please update me here. I think you stumbled over a strange defect. Jan

medini_1005899080

Hi Jan, as far as I understood your question, I did this already. A had only one trace mapping (FTTI) --> worked fine with import, do not worked with export (push) (seperate Ticket). Then I added the second one and tried to "push". Sven

medini_1024169437

Strange, I found this issue on the official KIL (Known Issue List) for medini but it says there that it at least should work when you add the second and pull. Does at least pull work? Jan

medini_1024169437

Sven, seems this issue as fixed in 22.2. In addition: any reason you map to Trace and not to other medini relations and Contribution?