- Issue created by @Chris Matthews
- Issue was unassigned.
- 🇬🇧United Kingdom andrew robinsonI agree with the intention to make these options consistent. 
 However, a user with only Edit permission for a content item is able to deselect the "Create new revision" checkbox when editing the item
 so the statement
 Users with the "Administer content" permission will be able to override this option.
 is misleading.The same applies for media. I propose changing the descriptions for the "Create new revision" options to: 
 Automatically create new revisions. This option can be overridden when content is edited.
 and
 Automatically create new revisions. This option can be overridden when media is edited.
- 🇮🇳India abhijith sCreated patch based on suggestion from #3. Please review. 
- last updateover 2 years ago 29,559 pass
- Status changed to Needs reviewover 2 years ago 12:35pm 27 June 2023
- Status changed to RTBCover 2 years ago 4:52pm 11 July 2023
- 🇺🇸United States smustgraveThis is actually such a small change that I think it doesn't need a full usability group review. Will ask @lauriii though. 
- 🇫🇮Finland lauriii FinlandI don't think this needs a full on usability review 
- 🇳🇿New Zealand quietoneI am doing triage on the core RTBC queue → . This issue is changing the user interface so should be tagged 'usabiilty'. I'm adding the tag. I read the Issue Summary, the comments and the patch. There are no unanswered questions. The proposed resolution is not correct, the suggestion in #3 was taken. I decided to apply the patch and test. On Drupal 11.x, standard install. It works as stated in #3. I am uploading the screenshots I took. 
- 🇫🇮Finland lauriii FinlandIt looks like I filed a duplicate issue to this: 🐛 "Create new revision" is overridable regardless of permissions Needs review . I think it would be great to get are review that it's fine to change the description in the UI to match the current behavior instead of changing the behavior to match how the UI describes it. 
- 🇨🇭Switzerland berdir SwitzerlandCommented over there and basically came to the conclusion that I agree with updating the description. This issue doesn't seem to deal with sticky/promote flags yet, which also are currently controlled by the administer nodes permission (which is a super weird permission FWIW, since bypass node access and access content overview permissions have been split off from it it's really just all the cruft that didn't match the other two). 
- Status changed to Needs workalmost 2 years ago 8:04pm 9 November 2023
- 🇺🇸United States xjmActually, I do think this needs UX review, because it's undoing a previous UX initiative's work to remove as many descriptions from forms as possible. In general, we should try to create a label that gives you all the information you need, and remove descriptions wherever possible. I really don't think "Published" needs a description, for example. 
- 🇦🇺Australia acbramleyI agree with #11 I think the NodeTypeForm is ok as it is for now until those options are untangled from "administer nodes". I guess we could refine it to include that permission in the description but it only applies to some We should definitely fix the MediaTypeForm description though since it's incorrect. Also "Automatically publish" isn't really accurate, it's about what the default is.