Project

General

Profile

Actions

Enhancement #22859

open

Unfolding a compliance report displays blocks in a non-logicial alphabetical order

Added by Michel BOUISSOU over 1 year ago. Updated 5 months ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
UX impact:
It bothers me each time
Suggestion strength:
Want - This would make my life a lot easier but I can manage without
User visibility:
First impressions of Rudder
Effort required:
Name check:
To do
Fix check:
To do
Regression:
No

Description

Hello,

Unfolding a compliance report for a directive displays it as nested blocks sorted in nested alphabetical order that does't relate in any way to the order in which the corresponding technique is written, it's internal logic or the chronological execution order.

This is rather puzzling and makes difficult understanding the cause of an issue, or debugging a technique being written.

Please see attached as an example, the order in which a technique is written and the order in which its execution is reported.


Files

Screenshot_20230608_104945.png (162 KB) Screenshot_20230608_104945.png Logical order of a technique Michel BOUISSOU, 2023-06-08 11:02
Screenshot_20230608_105119.png (54.2 KB) Screenshot_20230608_105119.png Nested alphabetical order in the report Michel BOUISSOU, 2023-06-08 11:02
Actions #1

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.3.3 to 7.3.4
Actions #2

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.3.4 to 7.3.5
Actions #3

Updated by Alexis Mousset over 1 year ago

  • Target version changed from 7.3.5 to 7.3.6
Actions #4

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.6 to 7.3.7
Actions #5

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.7 to 7.3.8
Actions #6

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.8 to 7.3.9
Actions #7

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.9 to 7.3.10
Actions #8

Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 7.3.10 to 7.3.11
Actions #9

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 7.3.11 to 7.3.12
Actions #10

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 7.3.12 to 7.3.13
Actions #11

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 7.3.13 to 7.3.14
Actions #12

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 7.3.14 to 7.3.15
Actions #13

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 7.3.15 to 7.3.16
Actions #14

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 7.3.16 to 7.3.17
Actions

Also available in: Atom PDF