Pipeline Execution Policy scope UI displays only 100 projects when 300+ are configured - Potential Bug

Summary

A customer discovered a potential discrepancy between the actual number of projects configured in a Pipeline Execution Policy scope and the number displayed in the UI. The customer configured approximately 300 projects in the policy scope, but the UI only displays 100 projects, suggesting either a display limitation or undocumented restriction.

Steps to reproduce

1. Navigate to Security Policies configuration
2. Create or edit a Pipeline Execution Policy
3. Configure the policy scope to include a large number of projects (approximately 300)
4. Save the policy configuration
5. Review the policy in the UI to see how many projects are displayed in the scope

What is the current bug behavior?

When a customer configures a Pipeline Execution Policy with approximately 300 projects in the scope, the UI only displays 100 projects, creating uncertainty about whether:

• The policy is actually applied to all configured projects but the UI has a display limit
• There is an undocumented limit on the number of projects that can be included in a policy scope
• Only 100 projects are actually being affected by the policy despite 300 being configured

What is the expected correct behavior?

The UI should either:

1. Display all projects included in the policy scope, or
2. Clearly indicate when there are more projects than can be displayed (e.g., "Showing 100 of 300 projects"), or
3. Document any limits on the number of projects that can be included in a Pipeline Execution Policy scope

Possible fixes

This issue could be resolved by:

1. Investigating whether there is an intentional limit on projects in policy scope and documenting it
2. Fixing the UI to display all configured projects or provide proper pagination/indication of additional projects
3. Clarifying in documentation the maximum number of projects supported in Pipeline Execution Policy scope