[EPIC] Implement Advanced Relationship Field

[oidacra]

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

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. Create Basic Relationship Field Structure for Edit Contentlet #30515
   QA : Passed Internal Team : Falcon Type : New Functionality Type : Task +4
   
2. Implement Relationship Field Data Table with Mock Data #30523
   QA : Passed Internal Release : 24.12.20 Team : Falcon +3
   
3. Implement Existing Content Selection Dialog for Relationship Field #30524
   Team : Falcon Type : Task +2
   
4. [Spike] Investigate Contentlet API Endpoints for Listing/Filtering/Pagination Capabilities for the Relationship field #30650
   Team : Falcon Type : Task +2
   
5. [Relationship Field] : Expose REST Endpoint that returns fields that meet specific criteria #30796
   QA : Passed Internal Release : 24.12.10 Team : Falcon Type : New Functionality dotCMS : Content Management +5
   
6. [Relationship Field] : Expose REST Endpoint to provide Content Search capabilities #30799
   QA : Passed Internal Release : 25.03.03 Sprint: Planned Team : Falcon Type : New Functionality dotCMS : Content Management +6
   
7. [Spike] Compile examples of Lucene queries based on filtering params #30911
   QA : Not Needed Release : 25.01.13 Team : Falcon Type : Task dotCMS : Content Management +5
   
8. Relationship Field: Listing Content with Dynamic Columns #30923
   OKR : User Experience QA : Passed Internal Release : 24.12.20 Team : Falcon Type : Enhancement dotCMS : Content Management +6
   
9. Relationship Field: Allow Choosing Content According to the Relationship #30928
   OKR : User Experience QA : Passed Internal Release : 25.01.07 Team : Falcon Type : Enhancement dotCMS : Content Management +6
   
10. Save and show relationships #31040
    QA : Passed Internal Release : 25.01.28 Team : Falcon dotCMS : Content Management +4
    
11. [EPIC] Relationship Field: Enable Static Fields for Search #31127
    Epic Sprint: Injected Sprint: Planned Team : Falcon Type : Task dotCMS : Content Management +6