Actions
Bug #18102
closed
Bug #18100: Techniques with conditions on tasks with very long parameters report "missing" parts on the dashboard
create a specific bundle specific for NA reports
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
to create NA reports, we define a class noop based on the technique name, technique parameters, and use it on reports, along with some old_class_prefix
But it may fail if parameter is too long (longer than 1000 characters) as content is added afterward
also, it can cause leaks of reports from one method to another
we could simply call a wrapper that would call the na report, and skipping the class definition part (as the class is non standart)
Updated by 
Updated by 
Updated by
Actions