Actions
Bug #25171
closedMessage « This node has no properties » on group
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
I dislike using that feature
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
97
Name check:
To do
Fix check:
Checked
Regression:
No
Description
When a group contains no nodes and it displays a « This node has no properties » message (where this is a group and not a node).
Even if properties are added (and there is a “success” message), the property is not displayed and the « This node has no properties » message still shows.
Files
Updated by Clark ANDRIANASOLO 4 months ago
- Category set to Web - UI & UX
- Target version set to 7.3.17
- Severity set to Trivial - no functional impact | cosmetic
- UX impact set to I dislike using that feature
- User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
- Effort required set to Very Small
- Priority changed from 0 to 100
Updated by Alexis Mousset 4 months ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset 4 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Clark ANDRIANASOLO
- Pull Request set to https://github.com/Normation/rudder/pull/5804
Updated by Alexis Mousset 4 months ago
- Target version changed from 7.3.17 to 8.1.7
Updated by Alexis Mousset 4 months ago
- Status changed from Pending technical review to In progress
- Assignee changed from Clark ANDRIANASOLO to Alexis Mousset
Updated by Alexis Mousset 4 months ago
- Status changed from In progress to Pending release
Applied in changeset rudder|2b9a45ab8e666489a1a4c9e62615422fbd681166.
Updated by Clark ANDRIANASOLO 3 months ago
- Priority changed from 100 to 98
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ 2 months ago
- Status changed from Pending release to Released
- Priority changed from 98 to 97
This bug has been fixed in Rudder 8.1.7 which was released today.
Actions