Actions
Bug #8141
closed
On rules creation, we may get a never stopping spining wheel on rules list
Added by Nicolas CHARLES over 8 years ago. Updated over 2 years ago.
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
When we create a Rule, promise get generated. While it is not fully generated, info for expected reports are not available, and so we get a spining wheel when showing compliance (for rules and reports)
But, the wheel never stops to spin, unless we reload page after end of generation
It should stop at some point (and even never start when compliance is disabled)
Updated by Nicolas CHARLES over 8 years ago
if rules isn't applied to nodes, the spinning wheel will never ever end
Updated by Nicolas CHARLES over 8 years ago
- Translation missing: en.field_tag_list set to sponsored
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.15 to 3.0.16
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.16 to 3.0.17
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.0.17 to 2.11.23
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.23 to 302
Updated by Alexis Mousset over 8 years ago
- Target version changed from 302 to 3.1.12
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.12 to 3.1.13
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.13 to 3.1.14
Updated by François ARMAND about 8 years ago
- Related to Bug #7336: Node stuck in "Applying" status added
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Jonathan CLARKE over 7 years ago
- Severity set to Trivial - no functional impact | cosmetic
- User visibility set to Getting started - demo | first install | level 1 Techniques
Updated by Jonathan CLARKE over 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
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.20 to 3.1.21
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.21 to 3.1.22
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.22 to 3.1.23
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.23 to 3.1.24
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.24 to 3.1.25
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 3.1.25 to 387
- Priority changed from 60 to 66
Updated by François ARMAND almost 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 almost 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 almost 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 Vincent MEMBRÉ almost 7 years ago
- Target version changed from 387 to 3.1.25
Actions