cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

We are aware of an issue causing intermittent login problems for some users following a recent update. Learn More

Translate the entire conversation x

Excel import of specification with inconsistent hierarchy

ME_12824198
4-Participant

Excel import of specification with inconsistent hierarchy

Hello all,

 

I´m currently experimenting on the codebeamer capabilities of importing an excel specification. I have two different baselines of the excel specification and wanted to see how capable codebeamer is in comparing those baselines. 

I edited the files with the same VBA script to add the intendation to get the hierarchy into codebeamer which worked just fine with the first baseline of the excel file. After I imported the more recent baseline which includes some changes, some work items in codebeamer were removed out of the previous hierarchy and placed on the highest level in the tracker. Those affects work items which haven´t changed between the two baselines and also the intendation is identical in both excel files. Also there are work items with identical parameters (parent item in CB and intendation in excel) where one remains in the hierarchy and the other one is moved.

 

After I had discovered this behaviour I did another import of the recent baseline without changing anything in the excel file. Now some other work items have been moved out of the hierarchy and some of the work items which had been moved out of the hierarchy after the second import were now back at the place where they belong.

 

Has anyone else already seen this behaviour? Is there an upper limit for rows in excel when codebeamer struggles to compare them (the excel files have between 1600-1700 rows)? Or is there any other solution for this problem?

 

Attached you see the history of an affected work item. After the initial import I had created the baseline and then although I imported the same file twice, once the parent work item was removed and with the second import it was restored.

 

CB version: 2.1.0.0

 

Thanks for your support and best regards

Michael

ACCEPTED SOLUTION

Accepted Solutions

Hello @ME_12824198 ,

 

This is a known issue, and has been fixed in these versions of Codebeamer:

  • Corrected in Codebeamer 22.10-SP10
  • Corrected in Codebeamer 2.0.0.4
  • Corrected in Codebeamer 2.1.0.2
  • Corrected in Codebeamer 2.2

View solution in original post

1 REPLY 1

Hello @ME_12824198 ,

 

This is a known issue, and has been fixed in these versions of Codebeamer:

  • Corrected in Codebeamer 22.10-SP10
  • Corrected in Codebeamer 2.0.0.4
  • Corrected in Codebeamer 2.1.0.2
  • Corrected in Codebeamer 2.2
Announcements



Top Tags