Actions
Enhancement #22362
closed
Missing component path in CSV for directive compliance
Pull Request:
UX impact:
Suggestion strength:
Require - I need this to use Rudder as I intend
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Small
Name check:
To do
Fix check:
To do
Regression:
No
Description
When we export directive compliance in CSV, we miss the information that the component is in a (chain) of parent block. We need to add a column for that, with the block chain as a namespace (for ex block1 -> block2, or bloc1/block2 or something like that).
This is necessary to be able to rebuild the relevant compliance. Without that, we are not able to build the compliance from the CSV when block are present.
Updated by Alexis Mousset almost 2 years ago
- Category set to Web - Compliance & node report
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.3.0~rc1 to 7.3.0
Actions