Current Behavior

The Jira Assets API currently has a maximum page size limit of 25 objects per request to get objects. When working with large asset inventories, this requires multiple paginated API calls to retrieve all necessary data.

Problem Statement

The current 25 objects per page limit is significantly restrictive when working with environments that have hundreds or thousands of assets. This limitation creates several challenges: * Performance Impact: Retrieving large datasets requires numerous sequential API calls, significantly increasing response times

• Rate Limiting Concerns: Multiple requests increase the risk of hitting API rate limits
• Development Complexity: Additional pagination logic and error handling is required to manage multiple requests
• Resource Consumption: More API calls mean higher network overhead and increased processing time

Proposed Solution

Increase the per-page limit to at least 100 objects per page, with consideration for even higher limits (e.g., 200-500) similar to other Atlassian API endpoints.

Benefits

• Improved Performance: Fewer API calls result in faster data retrieval
• Better Developer Experience: Simplified integration code with less pagination complexity
• Reduced API Load: Fewer requests reduce load on Atlassian infrastructure
• Consistency: Aligns with pagination limits in other Atlassian products (Jira Core API supports up to 100 results per page

thanks