dotCMS / dotCMS/core

Enhancing Relationship PP Filtering: Adding Second-Level Related Content Option

Open
#31,400 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OKR : Customer Support Priority : 2 High Team : Maintenance Type : Defect
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Parent Issue

#31036

Problem Statement

After this PR (#31036), the client is now reporting that they receive too many items when sending a Contentlet with a relationship using PP.

Steps to Reproduce
  • Create a Content Type C with a single Text field called title.
  • Create a Content Type B with:
    A Text field called title.
    A relationship field rel pointing to Content Type C.
  • Create a Content Type A with:
    A Text field called title.
    A relationship field rel pointing to Content Type B.
  • Create a Contentlet for C and name it c1.
  • Create a Contentlet for B, name it b1, and relate it to c1.
  • Create a Contentlet for A and name it a1.
  • Create a bundle and add a1.
  • Generate the bundle using the "Everything and Dependencies" filter (Really it is going to happen with any of the filter).
  • Check the Manifest—you will see that c1 is included.
Acceptance Criteria

We want to add a new filter that includes second-level related content (such as c1 in the example). Meanwhile, the "Everything and Dependencies" filter should remain unchanged, excluding second-level related content as it did before.

dotCMS Version

latest in main

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

https://dotcms.freshdesk.com/a/tickets/29642
https://helpdesk.dotcms.com/a/tickets/29668

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing parent issue #31036 and the reproduction steps for the three-level related-content setup. The work is done when a new filter includes second-level related content such as c1, while the existing "Everything and Dependencies" filter continues to exclude it.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, content
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.