Project

General

Profile

Actions

Bug #7308

closed

Compliance in Rules Overview, does not match rule details

Added by Dennis Cabooter over 5 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
3
Assignee:
-
Category:
Web - Compliance & node report
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
42

Description

Compliance in Rules Overview, does not match rule details. See attached screenshots. Of course I tried to refresh using the Refresh-button, but that doesn not help.


Files

Rule details.png (77.1 KB) Rule details.png Dennis Cabooter, 2015-10-26 14:43
Rules overview.png (76 KB) Rules overview.png Dennis Cabooter, 2015-10-26 14:44
Rule details 2.png (131 KB) Rule details 2.png Dennis Cabooter, 2015-10-26 14:50
Actions #1

Updated by Dennis Cabooter over 5 years ago

Attached a better screenshot for the Rule Details.

Actions #2

Updated by Benoît PECCATTE about 5 years ago

  • Category set to Web - Compliance & node report
  • Target version set to 3.0.16
Actions #3

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.0.16 to 3.0.17
Actions #4

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.0.17 to 302
Actions #5

Updated by Alexis MOUSSET almost 5 years ago

  • Target version changed from 302 to 3.1.12
Actions #6

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.1.12 to 3.1.13
Actions #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions #8

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #9

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #10

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #11

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #12

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #13

Updated by Jonathan CLARKE about 4 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Getting started - demo | first install | level 1 Techniques
Actions #14

Updated by Benoît PECCATTE about 4 years ago

  • Priority set to 29
Actions #15

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #16

Updated by Jonathan CLARKE about 4 years ago

  • Assignee deleted (Vincent MEMBRÉ)
Actions #17

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #18

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #19

Updated by Benoît PECCATTE almost 4 years ago

  • Priority changed from 29 to 42
Actions #20

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #21

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #22

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #23

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.25 to 387
Actions #24

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 387 to 4.1.10
Actions #25

Updated by François ARMAND over 3 years ago

  • Status changed from New to Rejected

This ticket was linked to Rudder 3.0 and the compliance processing was almost totally rewritten since then. We didn't see that problem since that time, I'm closing the ticket but feel free to reopen if it's still present for you.

Actions

Also available in: Atom PDF