Actions
Bug #8020
closedBridge does not corrupt job when Core provides incorrect report attributes
Start date:
03/09/2017
Due date:
06/13/2017
% Done:
100%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
Description
I noticed this when attributes looks like [{"a": "b", "c": "d"}] but perhaps there are other cases when Bridge does not check attributes validity.
Actions