dotCMS / dotCMS/core

[DEFECT] Pagination doesn't reflect in Publishing Queue for users with limited permissions

Open
#35,031 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Problem Statement

When a user has limited content type permissions, the pagination in the Publishing Queue Status tab doesn't reflect the number of bundles they can actually see. For example, if a user can only view 3 bundles on the first page (1-50), and 4 bundles on the second (51-100), they are not consolidated onto the first page. The user must still manually paginate through each page to find all bundles they have permission to view.

Steps to Reproduce

https://github.com/user-attachments/assets/bfc78582-f7b4-4457-8176-d71796430667

Acceptance Criteria

The pagination count at the bottom should reflect the number of bundles the user has permission to view, not the total number of bundles in the system.

Bundles that the user has permission to view should be consolidated and displayed starting from the first page, regardless of which page they originally appear on.

A user should not need to manually paginate through pages to find all bundles they have access to — all accessible bundles should be surfaced and displayed together until 50 is hit and then pagination should occur.

dotCMS Version

Current Evergreen 26.02.27-01

Severity

Medium - Some functionality impacted

Links

https://dotcms.freshdesk.com/a/tickets/35820

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 tracing the Publishing Queue Status tab's pagination and permission filtering; the issue provides no file or test names. Reproduce with a user who can view only some bundles, then verify that accessible bundles are consolidated from the first page and that the count reflects only those bundles.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
authorization, backend, content
Issue type
Bug
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.