Actions
Bug #11842
closedUser story #11748: Node lifecycle: add a node state
Node in "ignored" state get a spinning wheel in place of compliance
Status:
Rejected
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
50
Name check:
Fix check:
Regression:
Updated by François ARMAND about 7 years ago
- Related to Bug #8030: When a node doesn't have expected reports, we have a spinning wheel in place of compliance added
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.9 to 4.1.10
Updated by François ARMAND about 7 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 7 years ago
- Related to Bug #7281: Compliance keeps on loading while expected reports are not available for a node or a rule added
Updated by François ARMAND about 7 years ago
- Related to deleted (Bug #7281: Compliance keeps on loading while expected reports are not available for a node or a rule)
Updated by François ARMAND about 7 years ago
- Is duplicate of Bug #7281: Compliance keeps on loading while expected reports are not available for a node or a rule added
Updated by François ARMAND about 7 years ago
- Status changed from In progress to Rejected
Duplicates #7281
Actions