Actions
Bug #16392
closed
Missing timezone in generation "started at"
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
78
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
Whe a policy generation is running, we can see a little info telling us when the generation started, but the timezone info is missing, making it irrelevant.
Could you add it? (displaying is UTC is OK if the +0000 is present)
Updated by François ARMAND about 5 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- 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 79
Updated by Raphael GAUTHIER about 5 years ago
- Status changed from New to In progress
Updated by Raphael GAUTHIER about 5 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/2685
Updated by Raphael GAUTHIER about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|619d311b88fe234da19ed875f6fb946627fec325.
Updated by François ARMAND almost 5 years ago
- Priority changed from 79 to 78
- Fix check changed from To do to Checked
Updated by Alexis Mousset almost 5 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ almost 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.16 which was released today.
Actions