Project

General

Profile

Actions

Bug #24953

open

Stale score rows in database for deleted nodes

Added by Clark ANDRIANASOLO 6 months ago. Updated 14 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - UI & UX
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I dislike using that feature
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Small
Priority:
84
Name check:
To do
Fix check:
To do
Regression:
No

Description

Since I installed early versions of 8.1 with the scores features (to be more precise, before #24940), I have accepted and deleted nodes.

But once a node was accepted then some time after, deleted, the score details and global score for the node remained in the database, which makes score charts inconsistent on the dashboard (the count is wrong and stale score values are still visible).

We should remove these stale rows when the webapp starts.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #24940: Compliance score are still kept for deleted nodesReleasedFrançois ARMANDActions
Actions #1

Updated by Clark ANDRIANASOLO 6 months ago

  • Related to Bug #24940: Compliance score are still kept for deleted nodes added
Actions #2

Updated by Clark ANDRIANASOLO 6 months ago

  • Subject changed from Stale score details rows for deleted nodes to Stale score rows in database for deleted nodes
Actions #3

Updated by Clark ANDRIANASOLO 6 months ago

  • Description updated (diff)
Actions #4

Updated by Clark ANDRIANASOLO 6 months ago

A workaround is available since the release of #24940 : accept the node, then delete it back

Actions #5

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 8.1.3 to 8.1.4
Actions #6

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 8.1.4 to 8.1.5
Actions #7

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 8.1.5 to 8.1.6
Actions #8

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 8.1.6 to 8.1.7
  • Priority changed from 90 to 89
Actions #9

Updated by Vincent MEMBRÉ 2 months ago

  • Target version changed from 8.1.7 to 8.1.8
  • Priority changed from 89 to 86
Actions #10

Updated by Vincent MEMBRÉ 14 days ago

  • Target version changed from 8.1.8 to 8.1.9
  • Priority changed from 86 to 84
Actions

Also available in: Atom PDF