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.
Updated by Ilja Zakharov almost 6 years ago
- Related to Bug #9019: Downloading and uploading of marks does not work added
Updated by Evgeny Novikov almost 6 years ago
- Priority changed from Urgent to Immediate
It seems to be a serious regression since before it worked.
Updated by Vladimir Gratinskiy almost 6 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Fixed in "fix_marks".
Updated by Evgeny Novikov almost 6 years ago
- Status changed from Verified to Closed
I merged the branch to master in aa3e6cc8.
Actions