Actions
Bug #12048
closedLifecycle UI elements (dropdown menu & display) looks bad
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
46
Name check:
Fix check:
Regression:
Description
There is 3 points to make consistant and pretty:
- UI dropdown to choose the lifecyle: see attached screenshot, missing some space around text (in Chromium 63).
- displaying of current lifecycle in node details summary page,
- lifecycle "capsule" in node list when the lifecycle is not default.
Files
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.3.0~beta1 to 4.3.0~rc1
Updated by Benoît PECCATTE almost 7 years ago
- Assignee set to Raphael GAUTHIER
- Severity set to Trivial - no functional impact | cosmetic
- User visibility set to Getting started - demo | first install | level 1 Techniques
- Priority changed from 0 to 47
Updated by Benoît PECCATTE almost 7 years ago
The label in node details could be improved too
Updated by Raphael GAUTHIER almost 7 years ago
- Status changed from New to In progress
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.3.0~rc1 to 4.3.0~rc2
- Priority changed from 47 to 46
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.3.0~rc2 to 4.3.0~rc3
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.3.0~rc3 to 4.3.0
Updated by François ARMAND over 6 years ago
- Subject changed from Lifecycle dropdown menu looks bad to Lifecycle UI elements (dropdown menu & display) looks bad
- Description updated (diff)
Updated by Raphael GAUTHIER over 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1898
Updated by Anonymous over 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|be673ae51e8889a46dbb1a56c017732dae7e13e0.
Updated by Alexis Mousset over 6 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.0 which was released today.
- 4.3.0: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions