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

Implement Advanced Relationship Field #30495

Open
6 of 10 tasks
Tracked by #25445
oidacra opened this issue Oct 29, 2024 · 0 comments
Open
6 of 10 tasks
Tracked by #25445

Implement Advanced Relationship Field #30495

oidacra opened this issue Oct 29, 2024 · 0 comments

Comments

@oidacra
Copy link
Member

oidacra commented Oct 29, 2024

Parent Issue

#25445

User Story

As a content editor, I want to be able to manage related content through a sophisticated relationship field interface, so I can efficiently create, edit, and maintain content relationships while having the flexibility to modify nested content on the fly.

Acceptance Criteria

  1. Content Relationship Management

    • Users can relate both existing and new content
    • Support for multiple content selections simultaneously
    • Display maximum 6 items per page with pagination
    • Implement scrollable table view for related content
    • Enable drag and drop functionality for reordering
    • Provide delete functionality for removing relationships
  2. Search Dialog Features

    • Implement a dialog box for content search
    • Enable multi-select functionality
    • Include pagination for search results
    • Provide real-time search by content name
    • Add "Apply" button for confirming selections
    • Show content status and last modified date
  3. Nested Content Editing

    • Implement sidebar editing functionality
    • Support for nested relationship fields (recursive)
    • Allow multiple sidebars for different depth levels
    • Maintain proper state management for nested edits
    • Provide clear navigation between nested levels
  4. UI/UX Requirements

    • Implement scrollable table interface
    • Center pagination when no helper text is present
    • Clear visual hierarchy for nested content levels
    • Intuitive drag-and-drop interface
    • Responsive design for sidebar transitions

Proposed Objective

Technical User Experience

Proposed Priority

Priority 2 - Important

External Links

image
image
image

Figma

Assumptions & Initiation Needs

Quality Assurance Notes & Workarounds

Test Cases to Consider:

  1. Multiple level nesting scenarios
  2. Performance with large datasets
  3. Multi-language content relationships
  4. Concurrent editing scenarios
  5. Search performance with large content sets
  6. Edge cases in nested relationship chains
  7. Multiple sidebar handling

Tasks

Preview Give feedback
  1. QA : Passed Internal Team : Falcon Type : New Functionality Type : Task
    dsilvam
  2. QA : Passed Internal Release : 24.12.20 Team : Falcon
    nicobytes
  3. Team : Falcon
    nicobytes
  4. Team : Falcon Type : Task
    nicobytes
  5. Team : Falcon Type : Task
    jcastro-dotcms
  6. QA : Passed Internal Release : 24.12.10 Team : Falcon Type : New Functionality dotCMS : Content Management
    nicobytes
  7. Team : Falcon Triage Type : New Functionality dotCMS : Content Management
  8. Team : Falcon Triage Type : Task dotCMS : Content Management
  9. OKR : User Experience QA : Passed Internal Release : 24.12.20 Team : Falcon Type : Enhancement dotCMS : Content Management
    oidacra
  10. OKR : User Experience Team : Falcon Type : Enhancement dotCMS : Content Management
    nicobytes
@oidacra oidacra changed the title Implement Relationship Field Implement Advanced Relationship Field with Multi-level Content Management Oct 29, 2024
@oidacra oidacra moved this from New to Next 1-3 Sprints in dotCMS - Product Planning Oct 30, 2024
@oidacra oidacra added the Epic label Oct 30, 2024
@oidacra oidacra changed the title Implement Advanced Relationship Field with Multi-level Content Management Implement Advanced Relationship Field Oct 30, 2024
@oidacra oidacra moved this from Future to Next 1-3 Sprints in dotCMS - Product Planning Nov 13, 2024
@john-thomas-dotcms john-thomas-dotcms moved this from Next 1-3 Sprints to Future in dotCMS - Product Planning Nov 13, 2024
@nicobytes nicobytes moved this from Future to Next 1-3 Sprints in dotCMS - Product Planning Nov 27, 2024
@nicobytes nicobytes moved this from Next 1-3 Sprints to Current Sprint Backlog in dotCMS - Product Planning Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Current Sprint Backlog
Development

No branches or pull requests

1 participant