Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Content Edit: Implement File field #29691

Open
4 of 5 tasks
Tracked by #25445
john-thomas-dotcms opened this issue Aug 21, 2024 · 0 comments
Open
4 of 5 tasks
Tracked by #25445

New Content Edit: Implement File field #29691

john-thomas-dotcms opened this issue Aug 21, 2024 · 0 comments

Comments

@john-thomas-dotcms
Copy link
Contributor

john-thomas-dotcms commented Aug 21, 2024

Parent Issue

#25445

User Story

As a content editor, I want to be able to easily populate a File field, by either selecting a file already in dotCMS, or adding a new file to dotCMS.

Acceptance Criteria

  1. Adhere to the UX design.
    • Designs for both fields are in the design system here.
  2. For the File field, provide the following options in the field (not in the popup):
    • Main field area:
      • Drag and Drop of Choose file to upload
    • Right-side Links:
      • Select Existing File
        • When selected, open a popup to select the file.
        • This popup should be the same as other content selection popups (such as in the Relationships field).
      • Import from URL
        • When selected, open a popup for the user to enter the URL.
        • If the URL doesn't resolve to an appropriate file, the popup should stay open and display the error (rather than closing).
      • Create New File
        • When selected, open the content edit window for a new file.
        • The "state" of the content edit window needs to be maintained, so that when the new file is saved, the user is returned to the original content item that contains the File field.
  3. By default, the content type for any new file should be dotAsset.
    • If the file is imported from a URL, we should choose the dotAsset content type as if the file had been dragged and dropped into dotCMS.
    • If Create New File was selected, the default content type should be the generic dotAsset.
  4. There must be a field variable to allow the content architect to specify a different file content type.
    • If this field variable is set, then the default content type for all new files should be what it specifies.

Proposed Objective

User Experience

Proposed Priority

Priority 2 - Important

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

Tasks

  1. QA : Approved QA : Passed Internal Release : 24.09.25 Team : Falcon Type : New Functionality dotCMS : Content Management
    dsilvam
  2. Merged NW Removed OKR : Core Features QA : Passed Internal Release : 24.10.02 Team : Falcon
    dsilvam
  3. OKR : Technical User Experience QA : Approved QA : Passed Internal Release : 24.10.16 Team : Falcon dotCMS : Content Management
    dsilvam
  4. OKR : Technical User Experience QA : Approved QA : Passed Internal Release : 24.11.11 Team : Falcon
    dsilvam
  5. 2 of 5
    Epic Team : Falcon dotCMS : Content Management
    nicobytes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

2 participants