Actions
Bug #9017
closedChange of a converted error trace does not lead to assotiated leaf reports similarity recalculation
Start date:
06/27/2018
Due date:
% Done:
100%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
Description
I have a mark and an unsafe report associated with similarity equal to 0%. When I create a new mark, copy obtained new converted error trace to the old one I expect similarity to be changed from 0% to 100% but nothing happens. Both marks after the change have the same attribute values and same error traces but associated leaf reports differ.
Actions