As a content architect, I want to be able to set a default location for the Site and Folder field in a Content Type, so my users can easily select appropriate folders for their content.
We already have a defaultFolder field variable, which sets a default path for the file selection popup. This field variable is currently respected by the Binary, Image, and File fields, but is not respected by the current Site or Folder field.
We need to make sure the Site or Folder field in the new content edit screen respects the defaultPath field variable.
Acceptance Criteria
If the following conditions are all true, the site/folder selection popup opens with the specified site or folder selected:
The defaultPath field variable is set.
The value of the field var points to a valid site or folder.
The current user has permissions to view the specified site or folder.
If any of the above conditions are not met, the site/folder selection popup opens with the root of the current site selected.
When the Site or Folder field is edited, if the value of the defaultPath field variable points to an invalid folder, the user receives a notification.
But even if the field var points to an invalid path, the changes to the field var are still saved.
Proposed Objective
User Experience
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Parent Issue
No response
User Story
As a content architect, I want to be able to set a default location for the Site and Folder field in a Content Type, so my users can easily select appropriate folders for their content.
We already have a
defaultFolderfield variable, which sets a default path for the file selection popup. This field variable is currently respected by the Binary, Image, and File fields, but is not respected by the current Site or Folder field.We need to make sure the Site or Folder field in the new content edit screen respects the
defaultPathfield variable.Acceptance Criteria
defaultPathfield variable is set.Proposed Objective
User Experience
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response