Bug #4151
closed
Correct English in "change message" pop-ups
Description
The use of English language is not clear / precise / appropriate leading to potential confusion amongst users regarding the use and configuration of 'change messages'.
For example the default text to display known as "explanation to display" is:
"Please enter a message explaining the reason for this change"
Better:
"Please enter a reason explaining this change"
Also 'explanation to display' may well be better expressed as 'help text'.
Thus if 'messages' becomes 'reasons' then one would perhaps better say 'enable change audit|control' rather than 'enable change messages'.
This impacts all text referring to change messages.
Updated by Jonathan CLARKE over 10 years ago
- Status changed from New to Discussion
- Assignee changed from Jonathan CLARKE to François ARMAND
It seems to me that there are two issues here, given the impact and priorities:
- The wording for the default text to display known as "explanation to display" that could be improved to be more clear / precise / appropriate. Let's use Ed's suggestion, "Please enter a reason explaining this change"
- The name of the "change message" feature itself. I'm not sure what it should be renamed to, yet.
I think that 1 can be considered a bug fix and changed ASAP in all applicable versions.
I think that 2 is more impacting and should be a user story for a new release (2.9?).
François, can you create the corresponding tickets and assign work please?
Updated by François ARMAND over 10 years ago
- Subject changed from Change messages to Change the explanation message in "change message" pop-ups
- Status changed from Discussion to 8
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Priority changed from N/A to 3
- Target version changed from Ideas (not version specific) to 2.4.12
The new feature is #4153.
This ticket will track the first (wording of explanation message): change then explanation message:
"Please enter a message explaining the reason for this change"To:
"Please enter a reason explaining this change"
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from 8 to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/369
Pull request here: https://github.com/Normation/rudder/pull/369
When merging in 2.8 another change should be done directly in configuration service
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset c5a24163fea4727f86fe3678f8b504e7fa68f541.
Updated by Anonymous over 10 years ago
Applied in changeset 34680900a2c2228ac0a11309665e3001d64bee9f.
Updated by Vincent MEMBRÉ over 10 years ago
Corrected in 2.8 by merge commit 89c56228f7ebde5c1e93b403bc2c6b5dea783e2d
Updated by Nicolas PERRON over 10 years ago
- Subject changed from Change the explanation message in "change message" pop-ups to Correct English in "change message" pop-ups
Updated by Nicolas PERRON over 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.4.12 which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-November/000061.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog24
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/