yeln4ts

Indeed it would be great. It's not a priority right now but I'll definitely look into that.

yes it would be great. It's not the priority right now but hopefully one day

You must have check the box to hide findings in the Audit Type

You are right I will look into that as it also concerns Audit Types sections

This is good suggestions. It is definitely on my roadmap to improve the import/export functionalities.

For now it won't be possible as Categories are not really meant to be used as Audit Type since a Category contains custom fields it is not possible to change...

You can access findings directly by categories in the template like this: ``` {#categories} {categoryName} {#categoryFindings} ...usual stuff... {/categoryFindings} {/categories} ``` Or you could use conditions comparison: ``` {#findings} {#category...

Like I said since categories contain custom fields, changing it would be problematic as it would reset all custom fields to the new category. The better way is to focus...

I understand your point, it would need thinking though. How would you handle adding the vulnerability to an Audit, then the finding would have 2 vulnerability types (an array). What...

If a solution is found it should cover all use-cases, especially the problematic about choosing the right type to display in your report if there are multiple available.